Consolidate content versioning

[licitdev]

Scope

What's changed:

• Added a new delta field to the directus_versions table
  • Contains the final delta which is the combination of all revisions

Potential Risks / Drawbacks

• Updates to existing revisions during the migration may result in an incorrect final delta stored
  • This happens when an existing instance of Directus is performing the patch
  • The final delta could be fully repopulated in a subsequent release

Review Notes / Questions

• The existing versions field in the directus_revisions table will be removed in a subsequent release
• If the delta field in directus_versions is empty, the existing behaviour of fetching from directus_revisions remains
• Needs further testing to ensure content versioning remains fully operational

---

Related to #17894

[changeset-bot]

🦋 Changeset detected

Latest commit: d50f17a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 21 packages

Name	Type
@directus/system-data	Patch
@directus/types	Patch
@directus/api	Patch
@directus/sdk	Patch
@directus/utils	Patch
@directus/composables	Patch
@directus/extensions-sdk	Patch
@directus/extensions	Patch
@directus/themes	Patch
@directus/validation	Patch
directus	Patch
@directus/env	Patch
@directus/extensions-registry	Patch
@directus/memory	Patch
@directus/pressure	Patch
@directus/storage-driver-azure	Patch
@directus/storage-driver-cloudinary	Patch
@directus/storage-driver-gcs	Patch
@directus/storage-driver-s3	Patch
@directus/storage-driver-supabase	Patch
create-directus-extension	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[br41nslug]

So far working well in my tests versions get properly migrated and seem to function as expected/before in my tests.

Just this one question about the fallback but thats not a blocker as it should already be an edge case to get there.