Summary

Fix Telegram config/status accessors so read-only metadata paths (allowFrom, defaultTo) do not strict-resolve botToken SecretRefs.

openclaw status can currently fail when Telegram uses a valid file-backed SecretRef:

channels.telegram.botToken: unresolved SecretRef "file:filemain:/telegram/botToken". Resolve this command against an active gateway runtime snapshot before reading it.

The runtime account resolver should still resolve tokens strictly. This PR only adds a config-only accessor account for status/allowlist/default-target metadata, using mergeTelegramAccountConfig instead of resolveTelegramAccount.

Fixes #74832.

Testing

pnpm exec vitest run extensions/telegram/src/shared.test.ts extensions/telegram/src/account-inspect.test.ts --config test/vitest/vitest.extension-telegram.config.ts
# 2 files, 15 tests passed

NODE_OPTIONS=--max-old-space-size=8192 pnpm exec tsc -p tsconfig.extensions.test.json --noEmit --pretty false
# passed