docs: scope the tracked-run naming rules as additive

The two rules validate_tracked_run_name enforces (<=30 chars, no leading u or
r) are specific to tracked runs. Phrasing them as the naming contract read as
exhaustive, which would mislead a reader who then hits the separate --name
charset behavior reported in DOC-1425 (unresolved: no eng verdict, and the
constraint is not in the SDK or in Union CreateRun, which rejects only a
leading 'u').

Co-Authored-By: docsy <docsy@union.ai>
Signed-off-by: Peeter Piegaze <1153481+ppiegaze@users.noreply.github.com>

Author: ppiegaze

content/user-guide/tasks/task-deployment/run-command-options.md

@@ -118,7 +118,7 @@ flyte run --tracked --tracked-strict my_example.py my_task
 
 ### Naming a tracked run
 
-Tracked runs are named `local-<id>` unless you pass `--name`. A name you supply must be at most 30 characters and must not begin with `u` or `r`, both of which are reserved for runs the platform names itself. A name that breaks either rule fails before the run starts.
+Tracked runs are named `local-<id>` unless you pass `--name`. Tracking adds two rules on top of the usual `--name` behavior: the name must be at most 30 characters, and it must not begin with `u` or `r`, both of which are reserved for runs the platform names itself. A name that breaks either rule fails before the run starts.
 
 ### Tracking every local run