chore(dashboard): drop misleading backup.requiredTier from configuration payload (#1212)

Cloud Backup has a per-provider tier: Custom S3 is open to every tier
(PR #1143) while Sencho Cloud Backup requires Admiral. A single
backup.requiredTier='admiral' on the configuration response misrepresented
that split, and no consumer ever read the field. Remove it from the
response interface and the response builder; update the frontend mirror
type accordingly. Annotate the backup block so the per-provider intent is
clear at the call site.

backend/src/routes/dashboard.ts

@@ -43,7 +43,6 @@ export interface ConfigurationStatus {
     provider: 'disabled' | 'sencho' | 'custom';
     autoUpload: boolean;
     locked: boolean;
-    requiredTier: 'admiral';
   };
 }
 
@@ -147,10 +146,13 @@ export function buildLocalConfigurationStatus(
       globalCrash,
     },
     backup: {
+      // Cloud Backup has a per-provider tier: Custom S3 is open to every
+      // tier; Sencho Cloud Backup requires Admiral. The row is rendered for
+      // every tier because Custom S3 is universally configurable, so no
+      // dashboard-level lock is meaningful.
       provider: cloudProvider,
       autoUpload: cloudAutoUpload,
       locked: false,
-      requiredTier: 'admiral',
     },
   };
 }

frontend/src/components/dashboard/useConfigurationStatus.ts

@@ -39,7 +39,6 @@ export interface ConfigurationStatus {
     provider: 'disabled' | 'sencho' | 'custom';
     autoUpload: boolean;
     locked: boolean;
-    requiredTier: 'admiral';
   };
 }