Copy Component fails when selecting a newer SRG version and a control has been previously deleted in the source component

[rlakey]

To reproduce.

• Create new component from the General Purpose OS SRG v2r3. This creates a component with 191 controls.
• Duplicate one of the controls say 3 times
• Delete one of the new contols
• Attempt a "Copy Component" operation on the previous component and select General Purpose OS SRG v2r4

The UI will show the following error and the postgresql logs will show the errors below.

2022-11-30 19:19:57.498 GMT [379498] ERROR: duplicate key value violates unique constraint "rule_id_and_component_id"
2022-11-30 19:19:57.498 GMT [379498] DETAIL: Key (rule_id, component_id)=(000194, 250) already exists.

[rlakey]

Some more interesting data points. When doing copy component and keeping the same SRG things work as expected. When doing copy component and selecting a newer SRG version and when no previously deleted rules exist a new component gets created but is NOT based on the new SRG version and new rules are added to the source component from the newer SRG version for all of its requirements.

Meaning given Component A based on GPOS v2r3...run a copy component and select GPOS v2r4. The outcome is...

• Component A has 382 rules now instead of 191 with the new rules being from GPOS v2r4 and
• a new Component B is created with 191 rules based on GPOS v2r3.