Parametrize legacy v3 command test to cover all commands

[Copilot]

Description

The test_cli_v3_scan test only verified the scan command, leaving 4 other legacy v3 commands (scan_status, ingest, test_connection, simulate_anomaly_detection) untested. This creates risk for undetected regressions like typos in command names.

Changes:

• Parametrized test to verify all 5 legacy v3 commands return exit code 3
• Renamed test_cli_v3_scan → test_cli_v3_legacy_commands for clarity

Checklist

• I added a test to verify the new functionality.
• I verified this PR does not break soda-extensions.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• collect.soda.io
  • Triggering command: /home/REDACTED/work/soda-core/soda-core/.venv/bin/pytest pytest soda-tests/tests/components/test_cli.py::test_cli_v3_legacy_commands -v (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)