Description of problem:

Creating an incremental version of a CCV when the content-views are configured to automatic use latest CV versions will update all CV, even if they're not touched by the incremental update.

Example
CCV1 contains CV1 1.0 and CV2 1.0

There is on the same Satellite a CV2 2.0

When creating an incremental update of CCV1 with errata to be include on CV1, a 1.1 version  will need to be created.

The incremental update does not modify CV2.

At the end of the incremental update, CCV1 contains CV1 1.1 and CV2 2.0. 

An incremental update should not touch components not being modified.

How reproducible:

Always

Is this issue a regression from an earlier version:

Unsure

Steps to Reproduce:

1. Create and publish a content-view called CV1 with content requiring an erratum.

2. Create and publish a content-view called CV2.

3. Create a composite content-view called CCV including CV1 and CV2. Mark the option "Always update to latest version" on CV1 or CV2 and make sure that 'Autopublish' is disabled for the CCV.

4. Publish a new version of CV2. Ensure CCV has not updated.

5. Create a incremental update of CV1 with hammer to add some errata contained on repositories included only on CV1. Make sure to use the `--propagate-all-composites true` flag to also update the CCV.

6. Look at the new CCV (version 1.1) and it will include CV1 1.1 and CV2 2.0

If the option "Always update to latest version" the procedure happens as expected the end result would be CCV version 1.1 containt CV1 1.1 and CV2 1.0.

Actual behavior:
Incremental update brings newer CV versions available.

Expected behavior:
Incremental update should only add the packages being added, and not update other CVs

Business Impact / Additional info: