Reuse TeamCity connections from JetBrains IDEs

### Area

Configuration (parameters, projects)

### Problem or use case

Users who already configured TeamCity in a JetBrains IDE want to avoid entering the same server connection again in the CLI.

### Proposed solution

Agree with the IDE plugin maintainers on supported configuration and credential-store access. Start with explicit import from one supported IDE/platform, with user selection when several servers exist.

Reuse a token only when accessible through the supported credential store. Preserve its permissions: an IDE token may support fewer operations than a CLI token. Explain permission limitations and offer normal CLI login when broader access is needed; importing cannot broaden a token.

Verify missing/locked credentials, multiple IDE versions and servers, existing CLI settings, and limited-scope tokens. Never print credentials. Shared storage or broader IDE permissions requires coordination with the plugin; this is not verified by a server-only probe.

### Alternatives considered

Keep separate CLI login, or initially import only server URLs. A shared credential store is another option requiring agreement between both tools.

### Contribution

- [x] I'd be willing to submit a PR (once it's `status:finalized`)

Start by identifying the CLI configuration and login entry points, then confirm the supported JetBrains IDE/platform and credential-store integration with its plugin maintainers. Done means explicit import supports multiple servers and IDE versions, handles missing or locked credentials and limited-scope tokens safely, preserves token permissions, and falls back to normal CLI login without printing credentials.

Written by the indexing model from the issue text.