GConf removal

[CameronNemo]

Tracking issue for GConf removal.

• gconfmm: can be removed at any time, nothing depends on it gconfmm: remove package #38864
• gconf-editor: can be removed with GConf
• vscode: dependency seems to no longer be valid Drop gconf dependency microsoft/vscode#65744
• python-gconf: for hamster-applet, gconf removal is WIP Port to GSettings projecthamster/hamster#470
• ogmrip: no clear migration path
• spotify: GConf dependency has since been removed
• qt6-location, qt6-position: unclear why these depend on GConf-devel; they do not link to GConf
• upwork: distfiles seem out of date, perhaps best to also remove this package?

[ndowens]

ogmrip builds without gconf-devel fine

[Duncaen]

I think we should get rid of GConf where we can, but keep the package itself in the repository for some time.
Thirdparty electron binaries will probably depend on it for some time and getting rid of it will add extra steps for people who want to use electron binaries resulting in more package requests for electron stuff.

[github-actions]

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.

[paper42]

@Duncaen it's been almost 3 years, do you think we can remove GConf now?

[Duncaen]

Seems fine.