[Feature Request] [Epic] Clean up and sort repository

The repository is a curious blend of

• documents that have been officially archived (see Drafts, Operational-Docs, but also deprecated documents in Standards),
• documents that are normative and subject to a rigid formal process (see Standards: PR in a very certain format plus loose consensus),
• documents that are kind of informational and follow the classical PR-based process (see Community-Governance),
• a testing suite that also follows the classical PR-based process,
• a compliance monitor that has never left the state of being a prototype and that would benefit from a simplified process, not least because it's basically a one-man show (as unfortunate as that may be).

So, I propose to clean things up a bit.

• documents from Drafts and Operational-Docs that are still worth reading are moved to the docs repo, the directories deleted from the main branch,
• introduce subfolders draft and deprecated below Standards (we need a new version of scs-0001 for that, plus minor adjustments in the tooling), so it's more clear at first glance what's normative and effective,
• not sure about Community-Governance; could go to docs repo as well, or moved to the website, (or even to the minutes repo? it's not meeting minutes, but it's similarly related to current time),
• otherwise, keep Standards and Tests (although the latter could easily be moved into a separate repository),
• clearly document conceptual interfaces between Standards, Tests, and compliance monitor:
  • official report format for check scripts, main script, and potentially audits,
  • versioning of the test suite, the scope yaml format,
  • the business logic of how to evaluate the compliance status of a subject,
• move that business logic into a separate software module (to be located in the vicinity of Tests),
• move the compliance monitor into a separate repository where I can push to main.

Potentially if we decide to split this repo, we could also archive this one and create a new one for the core. (We could even contemplate moving to Codeberg, but OTOH let's not make this endeavor even more complicated.)