Fix bundle (re-)loading

[hanneskuettner]

Scope

What's changed:

• Instead of skipping over already registered bundle extensions, update the directus_extensions bundle entry records when loading a bundle extension, by removing stale ones and adding new ones
• Instead of using database.insert I'm now using the extensionsItemService.insert, was there any reason it was not used before?

Potential Risks / Drawbacks

• This approach removes bundle extension entries that are no longer present, potentially losing the extension enabled state. In practice this should not matter, however.

Review Notes / Questions

• I would like Pascal to review this since he initially wrote this and might have some thoughts on it.

---

Fixes #21942, fixes #21946, fixes #21922

• Should also fix Bundle extension loading but not working in 10.10.1 #21758, to be checked

[changeset-bot]

🦋 Changeset detected

Latest commit: 7fc33d7

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

This PR includes changesets to release 2 packages

Name	Type
@directus/api	Patch
directus	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

[hanneskuettner]

Note on the potential fixing of #21758:

Currently this PR only inserts missing module entries and removes DB records of entries that were removed from the bundle (matched based on the bundle ID + folder / entry name). If we want, we can extend the scope of this PR to instead upsert all entries, since we're touching on it anyways.