Bump DBus stack take 2

[affederaffe]

What does the pull request do?

Bump Tmds.DBus.Protocol and Tmds.DBus.SourceGenerator.
This uses the "official" Variant system instead of the SourceGenerator provided one (which was removed).
Accept the explicit ignoration of the DBus spec and assume collapsed variants.

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

• Added unit tests (if possible)?
• Added XML documentation to any related classes?
• Consider submitting a PR to https://github.com/AvaloniaUI/avalonia-docs with user documentation

Breaking changes

Obsoletions / Deprecations

None

Fixed issues

#15655

[avaloniaui-bot]

You can test this PR using the following package version. 11.2.999-cibuild0048326-alpha. (feed url: https://nuget-feed-all.avaloniaui.net/v3/index.json) [PRBUILDID]

[maxkatz6]

@affederaffe since this PR has breaking changes, you need to run nuke ValidateApiDiff command locally (nuke tool needs to be installed, alternatively, you can run _build project with the same command directly).
As it looks like, some autogenerated dbus files were made internal, as they should be.

[affederaffe]

Only the PropertyChanges type was made internal as it should be, it was a mistake to make it public at first.
It is safe to make it internal as it is unusable by itself, all members that use this type (i.e. proxies with WatchPropertyChangedAsync) are already internal, so there cannot be any users of this api anyway.

[jmacato]

@affederaffe we still need to run the API validation regardless as it's a hard requirement for making stable builds at the moment