Spike - Add IDs to docs to trace a doc across versions

[RubenSandwich]

A spike of implementing linking doc IDs across versions in UDR

This will require the following work:

• Add UUIDs to UDRs docs frontmatter
  • I suggest we use UUID v4 as it has time as an input in generation which should make collisions very low IMO
• Add doc UUIDs to app/api/docsPathsAllVersions.json
• Extend app/api/content-versions/route.ts or make app/api/v2/content-versions/route.ts (I am leaning towards a v2, as this is quite a change.)
  • That when given a doc UUID it returns it's versions and paths
    • (The current version only return versions)
• Extend fetchValidVersions in dev-portal to hit the new API api/v2/content-versions and return not just versions but versions and paths
• Extend DocsVersionSwitcher's options to take a path for it's version and then use that option.path to construct it's href

Some tools around this that would be helpful:

• GHA that fails if a new doc doesn't have a UUID
• GHA that fails if in a version a UUID is reused

[github-actions]

Vercel Previews Deployed

Name	Status	Preview	Updated (UTC)
Dev Portal	✅ Ready (Inspect)	Visit Preview	Fri Jun 13 20:01:19 UTC 2025
Unified Docs API	✅ Ready (Inspect)	Visit Preview	Fri Jun 13 19:55:40 UTC 2025

[github-actions]

Broken Link Checker

No broken links found! 🎉