Install rule-driven UTC library service configuration

[JaxCalder]

Install the packaged dmutc service template and RTC rule through standard flash manifest service/rules tags. dmdevfs reports RTC devices and libsystemd starts a library-backed UTC unit using the event path.

Validation: generated configuration contains both files; build and OpenOCD flash verified on STM32F746G-DISCO. After reset dmutc@rtc starts automatically with type=library and pid=0. UTC 6/6, RTC 12/12, RNG 6/6; PC UTC restored.

Depends on released library lifecycle support, dmdevfs RTC reporting, dmutc and registry registration. Validation uses ignored local build manifests; no local paths or pins committed.

Implementation: choco-technologies/dmutc#1
Registry: choco-technologies/dmod-registry#17

Related implementation PRs:

• RTC reporting: Report RTC devices to libsystemd for device rules dmdevfs#73
• Generic library service lifecycle: Support per-unit lifecycle callbacks for library services dmsystem#8
• UTC library: Implement UTC library with rule-driven RTC services dmutc#1
• Boot configuration: Install rule-driven UTC library service configuration #132
• Ecosystem: Integrate RTC reporting and rule-driven UTC library services dmod-ecosystem#31
• Registry: Register dmutc UTC library dmod-registry#17

Additional dmboot integration regression: the existing CI Renode runner passed boot/log-ring access, UART/VFS, SD automount and persistence across remount, LCD and touch tests. A second run with the optional audio model also passed. A one-second 523 Hz tone completed with zero underruns; captured stereo channels agree and measure approximately 522 Hz.

The Renode network/TAP step was explicitly skipped because this host lacks root and a TUN device. Physical STM32F746G-DISCO checks passed DHCP, ping in both directions, telnet command execution and temporary root/SD file read/write. The ICMP library correctly rejects STOP while a dependent module uses it. The independent plain-library lifecycle regression passes; libsystemd now passes 63/63. No production code fixes were needed in this regression run. Raw validation logs remain local and are not published.

Follow-up network diagnosis: a single ping after idle returns 0/1; an immediate repeat returns 1/1. An outgoing board ping warming ARP is followed by 3/3 incoming responses. Released ICMP code sends replies inline on the sole RX pump, while its send path can block waiting for an ARP reply that this same pump must consume. This explains the cold-cache loss and predates these UTC/library-service changes. No networking implementation was changed. Network regression therefore remains qualified rather than declared loss-free.

The libsystemd GitHub CI passes with the 63-step suite. Raw logs remain local. Two small physical-board test files remain because rm is absent; installing an additional removal tool was rejected by automatic approval review. No extra executable was installed on the board.