Description of problem:

When a Composite Content View is created, a corresponding content view environment is also generated. Once it is associated with a registered host, it becomes unclear which specific content view environment (out of those added to the Composite Content View) is being used to retrieve the content.

Is this issue a regression from an earlier version: Content View Environments are newly introduced in Satellite 6.17

Steps to Reproduce:

1. Create following content views on Satellite:

   i) RHEL_9_AppStream : With only one repository added to it which is RHEL9-AppStream

   ii) RHEL_9_BaseOS : With only one repository added to it which is RHEL9-BaseOS

   iii) RHEL-9 : With both RHEL9-AppStream and RHEL9-BaseOS repository added to it and also an Exclude Filter applied which will exclude errata starting from 01st Jan 2024 till today

2. Create a Composite Content View (RHEL9_CCV) and add all the above mentioned Content Views to it (RHEL_9_AppStream, RHEL_9_BaseOS and RHEL-9). Publish/promote a new version of RHEL9_CCV

Actual behavior:

i) A content view environment against the RHEL9_CCV is created: Library/RHEL_9_CCV

ii) The host registered with Satellite can be associated with the Library/RHEL_9_CCV content-view-environment successfully

iii) While running 'yum repolist -v' command, the package count against repository shows that RHEL-9 content view is not considered and packages are fetched from repositories added to  RHEL_9_AppStream and RHEL_9_BaseOS content view

Expected behavior:
i) The content-view-environment should not get created against a Composite Content View

ii) Even if the environment is created, it should not get associated with the host registered with Satellite/Capsule

 Additional info: If package count is not considered, it is difficult to identify the content-view-environment within CCV from where the repository is being fetched