Refactor test case file and folder structure

[tzifudzi]

What type of PR is this?

New feature

What this PR does / why we need it:

Helps organize the test cases such that each Ops Readiness Spec is in its own folder. This should make the test cases more easier to read through, and easier to maintain. Accompanying README.md will also assist with any additional information regarding the specification.

Previous structure

• testcases.yaml

New structure

• specifications/
  • core-concurrent/
    • README.md
    • spec.yaml

Which issue(s) this PR fixes:

• Data model improvements: It has rough edges #61
• Add a specifications/ directory w/ README #56

Testing

Ran automated tests in the project with all passing. Also ran manual tests against a local cluster to ensure no breaking changes have been introduced.

Sample output from test run ./op-readiness --provider=aws --kubeconfig=$KUBECONFIG --dry-run=true --category=Core.Network

2023-08-01T09:05:56-07:00       INFO    Discovered 9 test files for Windows Ops Readiness specifications Core.Concurrent, Core.Network, Core.Scheduling, Core.Storage, Extend.ActiveDirectory, Extend.HostProcess, Extend.Network, Extend.NetworkPolicy, Extend.Worker
2023-08-01T09:05:56-07:00       INFO    [OpReadinessTests] Skipping Ops Readiness Tests for Core.Concurrent because specification was not specified in category filter
...
2023-08-01T09:05:56-07:00       INFO    [OpReadinessTests] 1 / 1 Specifications - Running 10 Test(s) for Ops Readiness specification: Core.Network
2023-08-01T09:05:56-07:00       INFO    [Core.Network] 1 / 10 Tests - Running Operational Readiness test: Ability to access Windows container IP by pod IP
...
2023-08-01T09:06:10-07:00       INFO    Ran 1 of 6965 Specs in 0.012 seconds
2023-08-01T09:06:10-07:00       INFO    SUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 6964 Skipped
2023-08-01T09:06:10-07:00       INFO    [OpReadinessTests] Completed running Ops Readiness tests

Additional notes

All test cases have been migrated to new structure as is from the main branch with no further alterations e.g. if was commented I left it commented

[k8s-ci-robot]

Hi @tzifudzi. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[knabben]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: knabben, tzifudzi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [knabben]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment