Description of problem:
pulseaudio should not be triggered when a user logs in via SSH.
It seems to make no sense, so "KISS" alone would be a reason to request that.
Additionally, it leads to issues like bz1885553, where this happened:
a) user logins via SSH
b) pulseaudio started
c) bluetooth packages installed, triggered by pulseaudio in a way leading to a systemd crash
Let's just cut off the whole chain in preventing the first thing which seems to serve no purpose at all for SSH logins from remote: prevent pulseaudio from being run.

Version-Release number of selected component (if applicable):
All rhel8 versions affected, it seems

How reproducible:
always

Steps to Reproduce:

• Login as user via SSH (also happens for Xorg/Wayland, but might make sense then)

user@<uid>.service executes
this spawns "systemd --user"

Actual results:
1. "systemd --user" sets up pulseaudio.socket (listening on /run/user/<uid>/pulse/native) as part of reaching sockets.target
this is because pulseaudio.socket is installed (/usr/lib/systemd/user/sockets.target.wants/pulseaudio.socket)

2. "systemd --user" sets up pulseaudio.service as part of reaching default.target
this is because pulseaudio.service is installed (/etc/systemd/user/default.target.wants/pulseaudio.service)

2.) is then in our other scenarios leading to issues.

Expected results:
Pulseaudio should not be triggered when a user logs in via SSH.