Create database constraints for approver group names and migrate existing data

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Work on this issue
• Close this issue

Summary

We recently added validation to prevent users creating approver groups with the same name.

As part of this, we should also create database-level constraints and migrate existing data that have duplicates. See: !16216 (comment 213395600)

Improvements

Prevents inconsistent data state at the database level.

Risks

Data migration might be tricky?

Involved components

Optional: Intended side effects

Optional: Missing test coverage