Run local commands with TeamCity environment parameters

### Area

Configuration (parameters, projects)

### Problem or use case

Developers want to reuse a job’s non-secret environment settings when running a local command, without copying parameters manually.

### Proposed solution

Start with `env.*` parameters from one explicitly selected job, stripping the prefix when mapping them to environment variables. Decide whether the first interface exports values or runs a child process; it need not do both.

Define inheritance, unresolved references, and collisions with local environment variables. Job configuration values and a completed run’s resulting parameters are different sources; do not promise branch-specific runtime resolution from a job query.

Skip password parameters with a clear indication. REST does not provide their plaintext values, so an `--allow-secrets` flag cannot recover them. Do not map `system.*` or arbitrary configuration parameters into environment variables by default.

Verify quoting, multiline values, unresolved references, secret omission, and environment precedence. The live server exposes resulting parameter names, but this audit did not retrieve secret values.

### Alternatives considered

Use existing parameter commands or `teamcity api` with a local script. Keep secrets in the developer’s existing secret-management workflow.

### Contribution

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