I never had a "redis@basename" instance! Yet after todays dup to 20240624 which
replaced redis with valkey-7.2.5-2.1.x86_64 the migration logic enabled these
bogus services, which naturally failed during boot:

```
~> ll /etc/systemd/system/multi-user.target.wants/valkey*
lrwxrwxrwx 1 root root 39 Jun 26 08:10
'/etc/systemd/system/multi-user.target.wants/valkey@basename.service' ->
'/usr/lib/systemd/system/valkey@.service'
lrwxrwxrwx 1 root root 48 Jun 26 08:10
'/etc/systemd/system/multi-user.target.wants/valkey-sentinel@basename.service'
-> '/usr/lib/systemd/system/valkey-sentinel@.service'
```