Central pod in CrashLoopBackoff due to failed to persist groups to store error during 4.0 upgrade

Issue

• Red Hat Advanced Cluster Security (ACS) central-* pod in a CrashLoopBackoff state due to failed to persist groups to store error during 3.74.x to 4.0.2 upgrade
• The ACS central- pod fails its migration at step 167:

2023-06-22T21:17:38.464828098Z Migrator: 2023/06/22 21:17:38.464718 log.go:18: Info: Successfully updated DB from version 166 to 167
2023-06-22T21:17:38.638477629Z Migrator: 2023/06/22 21:17:38.638327 log.go:18: Info: failed to persist groups to store ERROR: duplicate key value violates unique constraint "groups_pkey" (SQLSTATE 23505)
2023-06-22T21:17:38.648557992Z Migrator: 2023/06/22 21:17:38.648456 log.go:18: Info: Migrator failed: migrations failed: error running migration starting at 167: moving groups from rocksdb to postgres: ERROR: duplicate key value violates unique constraint "groups_pkey" (SQLSTATE 23505)

• The ACS central-db is logging unique constraint errors for:

2023-06-22T21:17:38.632781773Z 2023-06-22 21:17:38.632 UTC [776] ERROR:  duplicate key value violates unique constraint "groups_pkey"
2023-06-22T21:17:38.632781773Z 2023-06-22 21:17:38.632 UTC [776] DETAIL:  Key (props_id)=() already exists.
2023-06-22T21:17:38.632781773Z 2023-06-22 21:17:38.632 UTC [776] CONTEXT:  COPY groups, line 2
2023-06-22T21:17:38.632781773Z 2023-06-22 21:17:38.632 UTC [776] STATEMENT:  copy "groups" ( "props_id", "serialized" ) from stdin binary;