fix: keep connector available during Telegram startup

[roymeshulam]

Problem

Telegram Connector startup could block before opening its health endpoint. On this Ubuntu 24 host, the bundled grammY runtime failed setMyCommands with a valid bot token, while the native installed runtime succeeded.

Proposal

• bind Connector health before external adapter initialization
• retain degraded adapter health instead of reducing it to a generic unavailable state
• bound Telegram startup work
• leave grammY and its retry plugin external to the Connector CJS bundle

Tradeoffs

The connector runtime now relies on its declared grammY dependencies being present beside the packaged service; the existing release/package flow should preserve declared production dependencies. This avoids the observed bundled-runtime incompatibility.

Verification

• pnpm -F @traderalice/connector-service test
• pnpm -F @traderalice/connector-service typecheck
• npx tsc --noEmit
• pnpm test
• live local check: valid Telegram token reached awaiting_link after restart; /link completed successfully.

[vercel]

@roymeshulam is attempting to deploy a commit to the luokerenx4's Team Team on Vercel.

A member of the Team first needs to authorize it.