feat(publish): move dbus-glib, setxkbmap, xorg-x11-server-Xwayland to rpm-base

[binujp]

Summary

Move three components from rpm-sdk to rpm-base publish channel to support the WSLg system distro migration to Azure Linux 4.0.

Motivation

The WSLg system distro container image builds against the base repo only. These packages are already built in AZL4 but published to the SDK channel, making them unavailable to the WSLg runtime image.

Components moved

Component	Reason
dbus-glib	Runtime dependency — D-Bus GLib bindings used by PulseAudio, Weston plugins
setxkbmap	Runtime utility — keyboard layout configuration (replaces retired xorg-x11-server-utils metapackage)
xorg-x11-server-Xwayland	Critical runtime — X11 application support under Wayland compositors

Changes

• Added all three to [component-groups.base-packages].components in components-publish-channels.toml (alphabetically sorted)

Testing

• All three components render unchanged (CHANGED: false) — publish channel does not affect spec content
• No build changes required; packages are already built successfully in rpm-sdk

Partially fixes AB#20772

[Copilot]

Pull request overview

Moves three already-built runtime components (dbus-glib, setxkbmap, xorg-x11-server-Xwayland) into the rpm-base publish channel so they’re available to WSLg’s system distro image build (which consumes only the base repo).

Changes:

• Added dbus-glib to the component-groups.base-packages.components list.
• Added setxkbmap to the component-groups.base-packages.components list.
• Added xorg-x11-server-Xwayland to the component-groups.base-packages.components list.

[reubeno]

Thanks for including testing details in the PR summary.

What did we do to confirm that this is a closure-preserving change? In other words, do any of the subpackages produced by the 3 named SRPMs have runtime dependencies on packages only in SDK?

[christopherco]

In the PR description, please add the bug item link. For example, AB#20772

[binujp]

Thanks for including testing details in the PR summary.

What did we do to confirm that this is a closure-preserving change? In other words, do any of the subpackages produced by the 3 named SRPMs have runtime dependencies on packages only in SDK?

I was able to install the three moved rpms. Verified the closure too.