fix(simulator_compatibility_test): use pytest runner to fix Jazzy CI failure

[xmfcx]

• Switch tests_require from [] to ["pytest"] so colcon uses the pytest runner instead of unittest
• Add [tool:pytest] with norecursedirs to prevent pytest from discovering manual simulator tests

Why

The Jazzy CI is failing with exit code 5 on simulator_compatibility_test.

This package is a manual simulator compatibility test suite -- all tests require a running simulator (e.g. MORAI SIM: Drive) and human observation, as described in the README. It has never had automated CI tests, and no tests ran on Humble either:

Starting >>> simulator_compatibility_test
--- output: simulator_compatibility_test
----------------------------------------------------------------------
Ran 0 tests in 0.000s
OK
---
Finished <<< simulator_compatibility_test [0.62s]

The root cause is a chain of issues:

1. setup.py had tests_require=[], which made colcon select the unittest runner instead of pytest.
2. The test classes in this package don't inherit from unittest.TestCase (they're pytest-style), so unittest discovered 0 tests on both distros.
3. Python 3.10 (Humble) returns exit code 0 for "Ran 0 tests" -- OK.
4. Python 3.12 (Jazzy) returns exit code 5 for "Ran 0 tests" -- NO TESTS RAN (new behavior).
5. The colcon unittest runner passes this exit code through directly, failing CI on Jazzy.

The fix switches to the pytest runner by setting tests_require=["pytest"]. The colcon pytest runner explicitly handles exit code 5 (NO_TESTS_COLLECTED) gracefully and does not propagate it as a failure. norecursedirs is needed because pytest has broader test discovery than unittest -- without it, pytest would find and attempt to run the manual simulator tests, which hang waiting for a simulator connection.

---

Test plan

• Verify Jazzy CI passes (previously failed with exit code 5)
• Verify Humble CI still passes (no behavior change -- 0 tests, pass)

[github-actions]

Thank you for contributing to the Autoware project!

🚧 If your pull request is in progress, switch it to draft mode.

Please ensure:

• You've checked our contribution guidelines.
• Your PR follows our pull request guidelines.
• All required CI checks pass before marking the PR ready for review.

[xmfcx]

The tests have passed, could you review?