revert the complete original payload on error flow events

[ferdinandlocksoftwares]

Adding @kartor

Scope

What's changed:

• Revert the original payload when using the 'request' or 'database' error flow events

Review Notes / Questions

• I would like to add this one once again as this was removed since from version 10.3 as this very important and been using this since start

---

Fixes #21249

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4947e68

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[ferdinandlocksoftwares]

@br41nslug can you help me on the check failed on unit test?

[paescuj]

The errors (@directus/errors) do not currently intend to hold any data except for the message. We would need to come up with a structure for that before proceeding with this PR. That's also why this data has been removed in 7daa775 (part of #18797).
Not sure if this PR is the right place to discuss this, though.

cc @rijkvanzanten

---

For this PR in particular:

• The unit tests (resp. the build) currently fail because the InvalidForeignKeyError doesn't accept a invalid field. So the error interface would have to be updated as well.
• If we're going to add that error data back, we should do so in a consistent manner for all DB vendors (and probably for other errors besides InvalidForeignKeyError too) - see again 7daa775