chore: migrate testdata to v1

[hbraswelrh]

Description

This PR migrates the test/test-data content from the v0.20.0 -> v1.0.0. The bad-*.yaml data is still expected to fail, but are migrated to the correct version. The Gemara MCP Server migration_assistant was used to bulk migrate and validate the artifacts.

Schema Changes

Schema Changes Made

• No schema changes
• Audit Log schema (auditlog.cue) changes
• Capability Catalog schema (capabilitycatalog.cue) changes
• Control Catalog schema (controlcatalog.cue) changes
• Enforcement Log schema (enforcementlog.cue) changes
• Evaluation Log schema (evaluationlog.cue) changes
• Guidance Catalog schema (guidancecatalog.cue) changes
• Mapping Document schema (mappingdocument.cue) changes
• Policy Document schema (policy.cue) changes
• Principle Catalog schema (principlecatalog.cue) changes
• Risk Catalog schema (riskcatalog.cue) changes
• Threat Catalog schema (threatcatalog.cue) changes
• Vector Catalog schema (vectorcatalog.cue) changes
• Other

Schema Change Details

<!-- If applicable, provide a brief summary or example of schema changes -->

Testing

• Unit tests added/updated
• Manual testing performed
• Test data updated (if applicable)

Related Issues

Reviewer Hints

• Use the Gemara MCP Server to validate the test/test-data changes

---

Self-review checklist

• This PR has content that was created with AI assistance.
  • I have read and followed the Generative AI Contribution Policy.
• I have the experience and knowledge necessary to answer maintainer questions about the content of this PR, without using AI.

[eddie-knight]

FWIW, we are on v1.1.0 now. Probably doesn't matter though.

[hbraswelrh]

FWIW, we are on v1.1.0 now. Probably doesn't matter though.

Cool. I can fix that just for consistency :)