chore: backport dd4c3ddadbb9 from chromium

[Molytho]

Chromium tries to bind to the newest version of some wayland interfaces. This causes issues when it doesn't actually support the version.
This patch ensures that only supported versions are bound to.

Fixes #32487
Backport of #32603

Notes: none.

[welcome]

💖 Thanks for opening this pull request! 💖

We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix.

Examples of commit messages with semantic prefixes:

• fix: don't overwrite prevent_default if default wasn't prevented
• feat: add app.isPackaged() method
• docs: app.isDefaultProtocolClient is now available on Linux

Things that will help get your PR across the finish line:

• Follow the JavaScript, C++, and Python coding style.
• Run npm run lint locally to catch formatting errors earlier.
• Document any user-facing changes you've made following the documentation styleguide.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[Molytho]

Can somebody please test it on gnome and kde. It work perfect under sway but after downgrading I noticed that it doesn't work with wlroots 0.14 because it passes a read-write file descriptor (which is technically not an issue but makes an assertion fail). The spec says the file descriptor should be mapped with MAP_PRIVATE which would need bigger adjustments.
As I except it to cause issues on non-rolling release distros/maybe gnome and kde it's maybe better to not merge it as it is.

[Molytho]

Now it should no longer cause any regressions. Now I manually mmap the file descriptor and munmap it afterwards. This approach is inspired by code I found in Chromium 96.

[release-clerk]

No Release Notes