Add types to async constraint validations

What does this MR do and why?

Follow up from !112838 (merged)

It adds an enum column to differentiate between constraint types. This will be usued in a follow up to implement check constraints validations.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #390651 (closed)