test: streamline Python test structure

[furionw]

Prior

Prior to this PR, we have inconsistent guidance on where we place tests

1. in lib/, we have src and tests at the same level
2. in components/, we have tests inside src

This can create confusion on locating test files.

additionally, the 2nd guidance doesn't bring clarify on how test in nested folder works. e.g. say we have

components/
|-- src/dynamo
    |--planner/
        |--foo/
            |--bar.py
    |--tests/

it's unclear which option should we go for

components/
|-- src/dynamo
    |--planner/
        |--foo/
            |--bar.py
            |--tests/
                |--test_bar.py  // option 1
    |--tests/
        |--planner
            |--foo/
                |--test_bar.py  // option 2

[coderabbitai]

Walkthrough

This pull request expands CI coverage for component tests and reorganizes the test directory structure by consolidating Python tests from per-component nested folders into a unified layout under tests/dynamo/.

Changes

Cohort / File(s)	Summary
CI Configuration .github/filters.yaml	Added components/tests/** filter path under core section to extend CI coverage for component tests
Test Structure Documentation tests/README.md	Reorganized documentation to reflect consolidated test layout, moving Python unit/integration tests from per-component nested tests/ folders into unified tests/dynamo/ structure with subdirectories for planner/, router/, vllm/, etc.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A rabbit hops with glee,
Tests consolidated, organized free!
CI filters expand their scope,
A better structure, a streamlined hope! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely summarizes the main change: reorganizing Python test structure for consistency.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The PR description clearly explains the problem (inconsistent test placement conventions), provides concrete examples, and details the solution adopted from existing patterns.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@tests/README.md`:
- Around line 23-34: Update the README text under the diagram so the bullets and
explanatory table refer explicitly to the new layout shown in the diagram (use
the components/tests/dynamo/<component>/... pattern rather than vague phrasing
like <component>/tests/ or dynamo/tests/); modify the three bullet lines and any
table rows that mention test locations to use the explicit
"components/tests/dynamo/<component>/..." wording and ensure examples and
descriptions match the diagram labels so there is no ambiguity.