Add --namespace flag to all scripts as alternative to NAMESPACE env var

Summary

Namespace is currently controlled via the NAMESPACE env var (defaulting to team1). Scripts should also accept a --namespace CLI flag so callers can specify it inline without prefixing every invocation with an env var assignment.

Affected scripts

• deploy-agent.sh
• deploy-benchmark.sh
• deploy-and-evaluate.sh
• evaluate-benchmark.sh

Proposed behaviour

• Add --namespace NAMESPACE to each script's argument parser.
• CLI flag takes precedence over the env var; env var takes precedence over the hardcoded default (team1).
• Pass --namespace through in wrapper scripts (deploy-and-evaluate.sh) the same way other flags are forwarded.

Motivation

Running parallel experiments in different namespaces (e.g. team2) currently requires either editing scripts or prepending NAMESPACE=team2 to every call. A --namespace flag makes this composable with other flags and easier to use in scripts and CI.

Related: #38 (OCP runner hardening), noted in PR #33 review by @kellyaa.

Start by reading the argument parsers in deploy-agent.sh, deploy-benchmark.sh, deploy-and-evaluate.sh, and evaluate-benchmark.sh, then compare how existing flags are forwarded by deploy-and-evaluate.sh. Done means each script accepts --namespace NAMESPACE with CLI-over-environment-over-default precedence, and the wrapper passes the flag through consistently.