Description of problem:

Client registered with Capsule associated with MultiCV should not list environments that are not synchronized with the Capsule server

Is this issue a regression from an earlier version: MultiCV is newly introduced on Satellite 6.17

Steps to Reproduce:

1. Navigate to Satellite WebUI → Administer → Settings → Content and set 'Allow multiple content views' to 'Yes'.

2. Create multiple Content Views (e.g., cv_1 & cv_2) and multiple Lifecycle Environments (e.g., 'Library' and 'Dev').

3. Publish new versions of all Content Views and promote them to the 'Dev' lifecycle environment.

4. Add only the 'Dev' lifecycle environment to the external Capsule, ensuring that the 'Library' lifecycle environment is not added. Then, synchronize the Capsule server.

5. Register the client to the Capsule server.

Scenario 1: Running the "subscription-manager environments --list" command on the registered client

Actual Behavior:
Running the command # subscription-manager environments --list lists the 'Library' lifecycle environment, which is not synchronized with the Capsule server:

       -------------------------------------------
       Environments
       -------------------------------------------
       Name:        Library
       Description: 

      Name:        Library/cv_1
      Description: 

      Name:        Library/cv_2
      Description: 

Expected Behavior:
Since the 'Library' lifecycle environment is not synchronized with the Capsule server, the # subscription-manager environments --list command should not list the 'Library' lifecycle environment.

Scenario 2: Running the hammer host update --content-view-environments command

Actual Behavior:
When trying to add a lifecycle environment to a host using the command # hammer host update --content-view-environments Library/cv_1, the following error is displayed:
"Could not update the host"

Expected Behavior:
The command # hammer host update --content-view-environments Library/cv_1 should throw a detailed error message, similar to the one produced by the # subscription-manager environments --set command, such as:
Validation failed: Host: Cannot add content view environment to content facet. The host's content source does not sync lifecycle environment 'Library'. (HTTP error code 422: Unprocessable Entity)