[beta] QtWebEngine 6.4 test builds

[tinywrkb]

Generate test builds with the current development releases of QtWebEngine 6.4 (Chromium 98), so users can try them and report back.

Already known regression is the addition of --webEngineArgs that needs to be set before any other WebEngine flag, i.e. --qt-flag webEngineArgs, and out-of-the-box enabled features that are set via a WebEngine flag won't work without explicitly setting the relevant flag after webEngineArgs.
For example, to have PipeWire screen sharing working, you would need to add WebRTCPipeWireCapturer after webEngineArgs, so the command to launch qutebrowser will look something like this:

flatpak run org.qutebrowser.qutebrowser --qt-flag webEngineArgs --qt-flag WebRTCPipeWireCapturer

[flathubbot]

Started test build 98742

[flathubbot]

Build 98742 failed

[tinywrkb]

bot, build org.qutebrowser.qutebrowser

[flathubbot]

Queued test build for org.qutebrowser.qutebrowser.

[flathubbot]

Started test build 98762

[flathubbot]

Build 98762 failed

[flathubbot]

Started test build 98763

[flathubbot]

Build 98763 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/96489/org.qutebrowser.qutebrowser.flatpakref

[flathubbot]

Started test build 100311

[flathubbot]

Build 100311 was cancelled

[tinywrkb]

I canceled the test build, as it looks like the CI's backlog is quite long due to failing instances that were not cleaned. This is a ~90min build run, so lets others use the current limited CI resources, and re-build later tonight.

[tinywrkb]

bot, build org.qutebrowser.qutebrowser

[flathubbot]

Queued test build for org.qutebrowser.qutebrowser.

[flathubbot]

Started test build 100357

[flathubbot]

Build 100357 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/98091/org.qutebrowser.qutebrowser.flatpakref