When a composite content view is both set to auto-publish and contains a content view set to 'Always update to latest version', it will update twice when an incremental update is applied on the child content view and the --propagate-all-composites flag is set.

How to reproduce:

1. Create and publish a content view with missing errata.
2. Add that content view to a composite content view and set the CV to 'Always update to latest version'. Set the CCV to auto-publish.
3. Run an incremental update on the CV with the --propagate-all-composites flag set:
   hammer content-view version incremental-update --content-view-version-id <cvv-id> --errata-ids <erratum-id> --propagate-all-composites true
4. Look at the new versions of the CCV. There will be a new minor version tracking the incremental update (X.1) and a new major version created in response to the new CV minor version (X+1).

Expected output
There are a few options for fixing this bug. Either

1. CCVs should not auto-publish on child CV minor version updates when the --propagate-all-composites flag is set,
2. --propagate-all-composites should not have an effect on CCVs set to auto-publish, or
3. auto-publishing CCVs should abort new publications when the new version's contents match the old version.

Option #3's approach is probably the cleanest but is also the most expensive. Any approach has lots of edge cases we need to worry about, unfortunately.