Description of problem:
When you create a composite content view, you need to update it separated from the CV of which it consits, what is not obvious

Version-Release number of selected component (if applicable):
6.0.6 (not available to choose yet)

How reproducible:
Always

Steps to Reproduce:
1. Create 2 CV (i.e. one of them Puppet)
2. Create a composite one included two before
3. Update one of the CV

Actual results:
The Composite CV does not reflect the changes, even if the Puppet CV is set to lastest version

Expected results:
Composite CV is updated with the new versions.

As an alternative:
- A message is shown saying "This CV is part of a Composite CV, you need to update the latest too"

As the preferred option:
- You can choose in Composite CV either a version number or "Latest". In that last case it is automatically refreshed when a new version of the underlying content view is promoted, if you choose a number that version is kept in the composite.


Additional info:
Due to the fact that you can only assign one CV to a system, this mechanism would allow simpler management of the CV.
For instance:
- I generate a CV for Basic RHEL
- I generate a CV for Puppet, this promotes very quickly compared to the former, and I can version it without having to update the former (good to know what I am doing and when)
- I generate another CV for syncrhoniziation of my own packages, again lifecycle of this is complete separated from the others.
- I add all of them into a Composite Content View and assign it to hosts. Whenever I do a change in some CV it is automatically reflected. If I want to keep functionality as of today I just choose one specific version for each underlying CV