Refactoring test_collections folder

[rquidute]

What changed

This PR is the phase-1 for the feature Python tests in TH UI.
The motivation to refactoring is to prepare the code to retrieve the python tests from SDK.
The final proposal for the folders organization is described bellow (PS: python_testing folder is part of phase 2):

• test_collections
  • sample_tests
  • python_tests
  • sdk_tests
    • sdk_checkout
      • .version
      • yaml_tests
        • yaml
      • python_testing
        • script
      • sdk_runner
    • support
      • yaml_tests
        • models
      • python_testing
        • models
      • init.py

Related Issues

Python tests in TH UI - Phase 1 (Refactoring test_collection folder) - project-chip/certification-tool#72

Testing

• Unit test updated and passing

• Test case execution successfully in TH (Automated, Semi-Automated, Simulated, Manual)

[mikaelhm]

I think it would be nice to keep a clear separation of content tracked in this repo and content pulled form the SDK repo.

I suggest that we organize it like this:

• test_collections/sdk_tests/sdk_checkout/ is the only place we put content from SDK, and it only contains content from the SDK
• test_collections/sdk_tests/support could contain all the python code we need in our repo, for yaml models etc. But no code from the SDK repo.

This way we can simply delete sdk_checkout when we need to update.

[mikaelhm]

Looks good.

But I think we can simplify the excluding of test_collections/sdk_tests/sdk_checkout