Release Service Testing "Packs" as Privateer Modules

## Feature Request

### Description of Problem:

- We want people on the internet (inc. Microsoft and LSEG) to be able to pick up CCC and run it against an environment they own, and find out if the controls are met.
- We should do this as privateer modules, since these already exist and are fairly well documented.

### Potential Solutions:

- This should combine the Cloud Abstraction API, Cucumber testing scripts , Standard Cucumber Steps, privateer etc.
- and do automated releases.
- These will be consumed elsewhere within the CCC repo for testing CFI configurations that are set up.
- As well as producing HTML, OCSF, we should also output Gemara assessment results.

### Other Considerations

1. We shouldn't be setting up users in the test scripts. This should be up to the person using the scripts, and the different accounts should be provided as configuration. Same goes for permissioning the users. This will actually make the scripts simpler to write and run.
2. For things like "log destination" or "remote vpcs", we should be providing all of this in the configuration/ environment file for the test. That means, we are being really strict about which service we are testing.. but we are able to inspect other services to check the interactions are working correctly.
3. We should write a GitHub action using an LLM to generate the gherkin testing steps based on releases of either the abstraction layer or changes to CCC catalogs
4. We should have some automatic validation code that is able to check that all of the testing steps can run. (Essentially like a compiler).
5. We should separate out all the tests by service. At the moment, several of our core tests overlap, it's not completely ideal.

@santoshmaurya-0x6275696c6473

- #994
- #996