Set up TeamCity and a first build from the CLI

### Area

Infrastructure (installation, release)

### Problem or use case

Setting up a repository in TeamCity involves server access, project/VCS configuration, and an available agent. The discussion covers several different starting points that need separate scopes.

### Proposed solution

Choose the first workflow before implementation:
- Connect a repository to an existing TeamCity server.
- Start a local evaluation server and agent.
- Provision a new TeamCity Cloud instance.

For the selected workflow, define prerequisites, authentication, user choices, resources created, retry behavior, and how to reach a first successful build. Local provisioning also needs explicit data retention and cleanup behavior. Testcontainer setup is useful prior work, not proof that a supported onboarding command is complete.

Kubernetes/Operator support remains a separate option. If pursued, support the user’s chosen kubeconfig context rather than assuming minikube, as requested in the comments. Command naming and cloud provisioning availability remain open. Do not promise a setup duration without measuring it.

### Alternatives considered

Compose existing login, project, VCS, and run commands; use the web setup flow or Docker/Operator documentation for provisioning.

### Contribution

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