Monorepo Structure

## Feature Request

### Description of Problem:

- @eddie-knight has already been working in this area - we need to be able to separate out taxonomy, threats and controls and release them independently. He's working on a Gemara release repository for receiving these.
- At the same time, we need to make the project much more approachable for either beginners or LLMs. This means, all fo the CCC source materials should be in a single repo, capable of performing multiple releases for the various different purposes. Currently, we're across at least two repos.

### Proposed Structure

Module | Path | Releases | Code Owner
-- | -- | -- | --
Capabilities | catalogs/capabilities | Gemara capabilities files | Sonali
Threats | catalogs/threats | Gemara threats | Security WG
Controls & Test Specifications | catalogs/controls | Gemara controls | Security WG
Cloud Abstraction Layer | modules/cloud-api | Go Modules | CFI WG (Rob, Santosh)
BDD Tests, Privateer Plugins | modules/plugins | Privateer Plugins | CFI WG (Rob, Santosh)
CFI Candidates + Test Runs (configuration required to test external CFI implementations) | cfi-testing | Gemara assessments | CFI WG (Rob, Santosh)
Website | website | ccc.finos.org | Website WG (Aric, Rob, Gabriele)

This is just a starter for 10. We also currently have the release toolkit, schemas... but I think these are moving out. And architectures could maybe go somewhere in website?