Limit tech admin contact operations via IS config

[nicholaspcr]

Summary

Closes #6323

Changes

• Add an contact info restriction error
• Add restrictions field to IS config, alongside the contact info restriction
• Update entities registries to validate contact if config is enabled

Testing

Unit tests and manual testing

Regressions

This is a new restriction on any flow that sets the admin/tech contacts which aren't done through the console. So I can't imagine a regression and most likely CLI users aren't setting those contacts since the old way still works (even with the deprecated warning).

Notes for Reviewers

Was going to do a testcase just for restrictions for each registry test file but it felt like overkill, let me know if the smaller tests found currently on the PR are appropriate enough.

If there are any lint errors on CI, I'll run the tests again after the format merge of the separate repository. Made the lint changes into a different PR just to remove it from this PR.

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
• Documentation: Relevant documentation is added or updated.
• Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
• Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.

[adriansmares]

Implementation LGTM in general. I have some naming concerns only.