Clarification on coexistence of wireplumber and pipewire-media-session

While testing out WirePlumber it become clear the way distros packaged it along with PipeWire itself could lead to some issues. I thought it would be best to have upstream clarification on what distros should do before opening issues for each package.

Should the Arch PipeWire package assume to always enable pipewire-media-session as here? While trying out WirePlumber with EasyEffects on Arch there was trouble with the pipewire-media-session service not being disabled since the pipewire package assumes the user will always want pipewire-media-session enabled.

Should distro packagers set wireplumber and pipewire-media-session to conflict, similarly to pipewire and pipewire-pulse? Fedora 35 conflicts between the two packages. Furthermore on Arch pipewire-media-session is a hard dependency of many pipewire packages, so effectively one must have it installed.