Fixes #38116 - Handle version removal for multi-CV hosts

[pavanshekar]

What are the changes introduced in this pull request?

Added checks for multi-CV host associations and helper methods to handle version removal from the environment, ensuring that relevant content facets and environment links are cleaned up. This ensures that only the targeted version is removed without affecting unrelated associations or environments.

Considerations taken when implementing this change?

Ensured selective removal of associations for multi-CV hosts to avoid reassigning hosts linked to single CVEs or impacting unrelated environments, while preserving existing associations and removing only the targeted version from the hosts' content facets. Existing methods were reused for consistency and to minimize duplication, and checks were added to handle edge cases, such as multiple hosts linked to the same environment, to prevent unintended side effects.

What are the testing steps for this pull request?

Create a multi-CV activation key

1. Promote a CV Version to multiple environments
2. Using Hammer CLI, update the activation key to use mutli CVE
   Example command: hammer activation-key update --organization="Default Organization" --id=1 --content-view-environments="ABC/cv1,XYZ/cv1"
3. Confirm that the activation key uses multi CVEs

Assign and register multiple hosts using the multi-CV activation key

Remove the version from the environment

1. Go to the CV associated with the activation key -> Versions
2. Click on the 3 dots of the respective CV Version and select the option "Remove from environments"
3. Follow the steps to remove the CV Version from the environment
4. A task will be created which should successfully remove the version from the environment when the CVE is in use by a multi-CV host

[jeremylenz]

Looks pretty good! some initial comments

[jeremylenz]

Tested and seems to work as expected, except for one comment below.

[jeremylenz]

Another edge case I found:

The correct content view environment label for "Library/Default Organization View" should just be "Library" (without the "Default Organization View").

I'm thinking it may be best to alter the rabl somehow to provide the correct content view environment labels, and then we wouldn't have to assemble them on the frontend..

[jeremylenz]

Works well and I feel much better about the logic now. Nice use of flatMap to find the correct content view environment :)

One more translation nit below, but feel free to merge :) ACK 👍