Tempo's CLI now requires the validator ID as a positional argument instead of a flagged one, representing a breaking change for all developers and node operators.

We've shipped a significant update to the Tempo command-line interface (CLI) that changes how validator IDs are handled. Previously, the validator ID was passed using a flagged argument, such as `--validator-id`. With this latest release, the validator ID is now a required positional argument, meaning it must be provided directly after the command without a flag. This change was implemented to streamline the CLI and reduce complexity for the most common operations. By making the validator ID a mandatory positional argument, we enforce its presence, preventing common errors where it might be accidentally omitted. This also aligns our CLI with standard conventions, making it more intuitive for new users and simplifying script creation by removing an unnecessary flag. This is a breaking change that requires immediate action from all developers and node operators. Any existing scripts, deployment pipelines, or manual commands that use the old `--validator-id` flag will fail. You must update your tooling to use the new positional argument format to ensure your validators and applications continue to function correctly with the latest version of Tempo.