Add bulk versions of all constraint management for Postgres

[ccutrer]

Motivation / Background

I've been doing a lot with migrations and Postgres, and noticed that when do a bulk table change, all the constraint-related management was running as separate statements, when it could all be run as part of a single ALTER TABLE.

Detail

This PR implements bulk versions of add and remove for foreign keys, check constraints, exclusion constraints, and unique constraints.

Checklist

Before submitting the PR make sure the following are checked:

• This Pull Request is related to one change. Unrelated changes should be opened in separate PRs.
• Commit message has a detailed description of what changed and why. If this PR fixes a related issue include it in the commit message. Ex: [Fix #issue-number]
• Tests are added or updated if you fix a bug or add a feature.
• CHANGELOG files are updated for the changed libraries if there is a behavior change or additional feature. Minor bug fixes and documentation changes should not be included.

I'm not sure if this qualifies as a large enough behavior change to warrant a CHANGELOG entry.

[fatkodima]

Did some implementation for check constraints before - #45208.