fix(avahi): bound restart time during rename flow

- add a 10 second timeout to the Avahi restart used after hostname changes
- before this change, the rename flow could wait indefinitely if the rc.avahidaemon script hung
- that was risky in onboarding because the user-facing reconnect path depends on this service refresh completing or failing predictably
- now the restart is bounded, logs a useful error on failure, and still rethrows so the existing strict mutation failure behavior is preserved

Author: Ajit-Mehrotra

api/src/unraid-api/avahi/avahi.service.ts

@@ -7,7 +7,14 @@ export class AvahiService {
     private readonly logger = new Logger(AvahiService.name);
 
     async restart(): Promise<void> {
-        await execa('/etc/rc.d/rc.avahidaemon', ['restart']);
-        this.logger.log('Avahi daemon restarted');
+        try {
+            await execa('/etc/rc.d/rc.avahidaemon', ['restart'], {
+                timeout: 10_000,
+            });
+            this.logger.log('Avahi daemon restarted');
+        } catch (error) {
+            this.logger.error('Failed to restart Avahi daemon', error as Error);
+            throw error;
+        }
     }
 }