New telepresence replace command.

[thallgren]

The new telepresence replace command simplifies and clarifies container replacement.

Previously, the --replace flag within the telepresence intercept command was used to replace containers. However, this approach introduced inconsistencies and limitations:

• Confusion: Using a flag to modify the core function of a command designed for traffic interception led to ambiguity.
• Inaccurate Behavior: Replacement was not possible when no incoming traffic was intercepted, as the command's design focused on traffic routing.

To address these issues, the --replace flag within telepresence intercept has been deprecated. The new telepresence replace command provides a dedicated and consistent method for replacing containers, enhancing clarity and reliability.

Key differences between replace and intercept:

1. Scope: The replace command targets and affects an entire container, impacting all its traffic, while an intercept targets specific services and/or service/container ports.
2. Port Declarations: Remote ports specified using the --port flag are container ports.
3. No Default Port: A replace can occur without intercepting any ports.
4. Container State: During a replace, the original container is no longer active within the cluster.

The deprecated --replace flag still works, but is hidden from the telepresence intercept command help, and will print a deprecation warning when used.

[thallgren]

Still a draft. Integration and docs are in the works.