minor pipewire-pulse naming differences

I'm doing some comparisons between pipewire-pulse (master) and real pulseaudio using pactl on Ubuntu 20.04.

It looks like names of bluetooth devices are a little different in pipewire-pulse

#In pulseaudio:
pactl set-card-profile bluez_card.00_1D_43_A0_A4_64 a2dp_sink_aptx

#In pipewire-pulse:
pactl set-card-profile bluez_card.00:1D:43:A0:A4:64 a2dp-sink-aptx

The use of the colons in the hw address in pipewire-pulse in the name causes pactl tab-completion to break in Ubuntu. Additionally, even if the ID of the card was the same, the use of dashes instead of underscores in a2dp-sink-aptx means I cannot use the same pactl CLI command to do the same thing for both pulseaudio and pipewire-pulse

Note the Bluetooth Sink name in pipewire-pulse does use underscores instead of colons:

#In pulseaudio:
pactl set-default-sink bluez_sink.00_1D_43_A0_A4_64.a2dp_sink

#In pipewire-pulse:
pactl set-default-sink bluez_output.00_1D_43_A0_A4_64.a2dp-sink

But again another inconsistency, the name is bluez_output in pipewire-pulse vs bluez_sink in pulseaudio. And the dash instead of underscore in ad2p-sink where all other spaces in the ID are underscores.

Same with sources:

#In pulseaudio
pactl set-default-source bluez_source.00_1D_43_A0_A4_64.headset_head_unit

#In pipewire-pulse
pactl set-default-source bluez_input.00_1D_43_A0_A4_64.headset-head-unit

However I think in this case the names blues_sink and bluez_source are added by the EHFive/pulseaudio-modules-bt plugin, and might not be held canonical, and bluez_input and bluez_output is more correct because that matches other source and sink types like alsa_input and alsa_output that both pulseaudio and pipewire-pulse use.