Fix primary key unique constraint error extraction for MySQL

[hanneskuettner]

Scope

MySQL does some weird stuff for primary key unique constraints errors, where it doesn't actually tell us the primary key, but instead yells PRIMARY at us. Handle this case in the error extraction logic and propagate that info up the stack to where we actually have the info about the primary key field name.

Additionally MySQL 5.7 won't even tell us the collection we're dealing with, so we have to add that in as well...

What's changed:

• Added primaryKey flag to the RecordNotUniqueError extensions to propagate error info
• Fixed handling for unique primary key constraints

Potential Risks / Drawbacks

None

Review Notes / Questions

• Should this sit this far up the stack, or should we pass more context to the translateDatabaseError function? I'm not sure 🤔

---

Fixes #15033

[changeset-bot]

🦋 Changeset detected

Latest commit: ce27114

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

This PR includes changesets to release 6 packages

Name	Type
@directus/api	Patch
@directus/errors	Patch
directus	Patch
@directus/extensions-registry	Patch
@directus/memory	Patch
@directus/validation	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