Add automatic test for the `ebpf_tracing.cmd`

Nobody has claimed this yet.

### Describe the feature you'd like supported

Add an automatic test for `ebpf_tracing.cmd` script, as per suggestion on #2357

### Proposed solution

Run the script with its supported scenarios, and check for the expected the outputs:

```bash
# Test #1
ebpf_tracing.cmd start "C:\_ebpf\logs"
- Tracing is started in the log folder, at least one log file is created

# Test #2 - The script should be left running for 'logman_period', eventually changing it artificially
ebpf_tracing.cmd periodic "C:\_ebpf\logs"
- An XML file is created for the rundown, in the committed directory
- ETL files are moved into the committed directory, except 'num_etl_files_to_keep'
- All files older than 'files_max_age_days' are deleted, eventually changing it artificially

# Test #3
ebpf_tracing.cmd stop "C:\_ebpf\logs"
- Log folder is deleted
```

### Additional context

_No response_

Start with the ebpf_tracing.cmd entry point and run its start, periodic, and stop scenarios against the stated log folder. Done means an automatic test verifies log creation, rundown XML and ETL handling, age-based deletion, and log-folder cleanup as described.

Written by the indexing model from the issue text.