Add telemetry for when user triggers testing from CLI

[Copilot]

This PR adds telemetry to capture when users run Python tests via the command line in the terminal. This helps us get a better understanding of testing usage in the extension outside of the testing UI.

Changes

• Added a new telemetry event constant UNITTEST_RUN_CLI to track CLI test execution
• Updated the telemetry interface to include the new event with proper GDPR comments
• Enhanced the terminal command detection to identify test commands:
  • python -m pytest, pytest, py.test
  • python -m unittest
  • python -m nose
• Added unit tests to validate the functionality

Implementation

The implementation uses the existing terminal command detection system that already tracks when users run Python scripts in the terminal. When a test command is detected, we send a specific telemetry event rather than the general REPL telemetry.

This implementation has minimal impact on performance as it just adds an additional condition to the existing command detection logic that already runs for every terminal command. The telemetry is sent asynchronously and doesn't block terminal execution.

Fixes #24562.

Warning

Firewall rules blocked me from connecting to one or more addresses

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

• cdn.fwupd.org
  • Triggering command: /usr/bin/fwupdmgr refresh (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 my firewall allow list

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[karthiknadig]

Remove nose. We don’t support that anymore.

[Copilot]

Remove nose. We don’t support that anymore.

I've removed nose test support as requested. All related detection code and test cases have been removed in commit 097da2d.

Comment addressed

[eleanorjboyd]

looks good to me- fixed linting as well. @karthiknadig am I good to take this out of draft and get reviews? [edit nvm]

[anthonykim1]

I think we can consolidate (lower.startsWith('python') && lower.includes(' -m pytest')) || (lower.startsWith('py ') && lower.includes(' -m pytest')) || (lower.startsWith('python') && lower.includes(' -m unittest')) || (lower.startsWith('py ') && lower.includes(' -m unittest')) ||
into two conditionals. One for starting with 'python' other for 'py'

[Copilot]

I've consolidated the conditionals as suggested into two statements - one for commands starting with 'python' and another for commands starting with 'py'. This makes the code more readable while maintaining the same functionality. All tests are passing. Changes in commit 6d2e428.