Replace old webkit2gtk in main with the one in webkit2gtk source package

[Tim Lunn]

I'm filing this as a new report, since previous discussions are split amongst atleast 2 different bugs [1]

The situation as it stands:
- Debian forked the webkitgtk source package when upstream dropped webkit1 from the releases, into webkit2gtk
- webkitgtk builds both webkitgtk and webkit2gtk-3.0 but the later can be disabled, easily enough
- webkit2gtk builds the current webkit2gtk-4.0, maintained version of webkit but is in universe
- As upstream apps are ported to webkit2gtk-4.0 they are either getting held back (yelp, devhelp) or reverted back to webkit1 (gnome-online-accounts)
- Upstream seems to be slowly porting from webkit1 to 2 but in some cases it quite a massive task.

I propose that we disable the webkit2 build in webkitgtk and promote webkit2gtk to main. The transition from webkit2gtk-3.0 to webkit2gtk-4.0 is trivial, and although the end result is 2 copies of webkit2 source in the archives, only the current maintained version will actually be built into binaries. This should atleast be better than the current situation, of having an obsolete build of wekit2gtk basically to keep webkit1 around

I realise there are some people out there that would prefer not to have any webkit in main, but as long as Ubuntu is relying on core GNOME packages, its unlikely to be avoidable.

[1] Bug 1469221 - Although that is more tracking the transition from webkit1 to webkit2, and probably not achievable this cycle, or even until upstream port evolution etc.
and some discussion in Bug 1466290

[Michael Terry (mterry)]

This sounds like something Jamie would like to weigh in on.