Connect musicdolphin's backend to irserver for the IR remote

The remote did nothing on musicdolphin: irserver received the keys, but the backend's
config had no lirc: section, on the belief that irserver could not speak lircd's
protocol. It can - irserver serves the lircd network protocol on port 8765, with lines
the backend's parser reads as they are - so point the backend there. The remote name
must match irserver's remote file exactly: "hauppauge", not lircd's "Hauppauge".

config.yml is install-once, so the running host was changed by hand the same way.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

roles/pi_musicmouse/files/config-musicdolphin.yml

@@ -68,10 +68,15 @@ general:
   # buttons, touch areas and tag scanner, none of which exist on a simulate-only
   # instance - it would publish a device of dead entities.
   #
-  # No lirc: section either, and consequently no top-level `remote:` mapping. This host
-  # uses mediapi_ir_control: irserver, a custom serial daemon on /dev/ttyUSB0; the
-  # backend's LircConfig speaks lircd's TCP protocol (pi_lirc, port 2222) and cannot
-  # talk to it.
+  # IR remote. This host uses mediapi_ir_control: irserver (the IRTrans receiver on
+  # /dev/ttyUSB0) rather than lircd, but irserver also serves lircd's network protocol
+  # on its own port 8765 - which is all the backend's LircConfig needs. The remote name
+  # is irserver's remote file, /usr/bin/remotes/hauppauge.rem, in lowercase. Number keys
+  # play whatever the top-level `remote:` mapping assigns them (none yet).
+  lirc:
+    host: "127.0.0.1"
+    port: 8765
+    remote_name: "hauppauge"
 
   # Backlight of the prev/next buttons while a figure is playing, 0..1. Inert here
   # (no mouse), kept so the file reads the same as the other hosts'.