chore(config): document keyvault diagnostics

What changed:
- Kept Key Vault startup warnings visible before app loggers exist.
- Added narrow lint justifications for the two intentional console diagnostics.

Warning impact:
- @bytelyst/config scoped warnings: 2 -> 0.
- Workspace warning total: 157 -> 155.

Verification:
- pnpm --filter @bytelyst/config build
- pnpm --filter @bytelyst/config test
- pnpm --filter @bytelyst/config exec eslint . --ext .ts,.tsx
- pnpm lint

packages/config/src/keyvault.ts

@@ -98,11 +98,13 @@ async function resolveAzureKeyVaultSecrets(
 
     const failures = results.filter(r => r.status === 'rejected');
     if (failures.length > 0) {
+      // eslint-disable-next-line no-console -- Startup secret-resolution diagnostics must remain visible before app loggers exist.
       console.warn(
         `[secrets] ${failures.length}/${missing.length} secrets failed to resolve — falling back to env vars`
       );
     }
   } catch {
+    // eslint-disable-next-line no-console -- Startup secret-resolution diagnostics must remain visible before app loggers exist.
     console.warn(`[secrets] Unable to connect to Key Vault at ${vaultUrl} — using env vars`);
   }
 }