GTK4/Wayland-ready release plan

[deltragon]

Hello!
I would like to detail my plan for merging and releasing the GTK4 port.

I think this is a big enough change to warrant at least a jump to version 2.3, if not version 3. Feel free to chime in on what you think it should be.
Before releasing it properly, I plan to do a beta release after everything is merged, followed by a Call for Testing of that beta release, so we ensure that the new version runs as smoothly as possible.

What should be contained in that release:

• The GTK4 work:
  • donotdisturb: fix changing interruptible fullscreen windows to normal mode #652
  • donotdisturb: switch x11 fullscreen detection to Xlib #655
  • port to gtk4 #561
• Wayland improvements:
  • Wayland: fix keyboard locking #651
  • Smartpause: add support for ext-idle-notify-v1 using pywayland #576

In my opinion, after this SafeEyes is, for the most part, Wayland-ready. We can also try and market the release as such.
I would also suggest merging the PRs in the order of this list.

What does not need to be in the release:

• Developer-side improvements:
  • migrate from setup.py to pyproject.toml #639
  • CI: add ruff linting job, fix PEP8/257 violations and formatting #615
  • pytest: test model.Break and model.BreakQueue #641

I think these are good to have long-term, but somewhat unrelated from the GTK4/Wayland changes.
Also, they are in some cases significantly more work to implement, so I would view these as long-term changes.

[deltragon]

Regarding internal testing:
I have tested my PRs sufficiently, in my opinion. I would argue for merging them as they are, and then testing the beta release in its entirety.

[deltragon]

Looking at the PRs merged since 2.2.2 again - maybe we should do a 2.2.3 release now, since it does contain some relevant bugfixes.
I'll see if I can prepare it the next few days.

[deltragon]

(And after 2.2.3 is cut, follow the plan above for the 3.0 release.)

[deltragon]

I have done the release. I did create an account for launchpad (deltragon, like on github), I can add the release there too. However, no hurry.