[CHORE] remove redundant variants from PermissionGroup

[kashif-m]

Feature Description

Few variants in PermissionGroup enum were kept in the application code for backwards compatibility. These variants are directly stored as TEXT in DB which forces the application to ensure backwards compatibility during staggered releases. Since new variants were added and deployed, old variants can be removed post running the DB migrations.

Possible Implementation

1. Add DB migration for updating any existing values from older variants to new variants
2. Remove variants from application code
3. Deploy

This still leaves a small time window where users can make use of older variants during staggered deployment once the migrations have run, that can be manually avoided by running migrations several times during staggered release, if required.

Have you spent some time checking if this feature request has been raised before?

• I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit a PR?

Yes, I am willing to submit a PR!