Description 

Problems with our curate task cause SyncList.repository's to have Collections that do not match the sync toggles. Of the 196 SyncList.repository, 108 had more Collections than expected, 14 had less Collections than expected.

There are also instances where a SyncList.repository has an expected Collection, but it has missing CollectionVersions for that Collection

Steps to Reproduce

• Sync your PAH with console.redhat.com
• See the Collections or Collection versions in your PAH `rh-certified` repo do not match console.redhat.com Automation Hub

Mitigation for this bug

• Remove curate tasks and have all SyncList.distributions include all Collections via AAH-1540, and rely on the v3/excludes endpoint to filter syncs. Mitigation is planned to deploy to c.rh.c May17.
• PAH galaxy_ng 4.5 clients include pulp_ansible `/excludes/` work and will have the sync match the sync toggle
• Other PAH clients (galaxy_ng 4.2, 4.3, 4.4) will sync all Collections regardless of the sync toggle, but there will be no missing Collections and no missing CollectionVersions 
• This mitigation also resolves related issues AAH-1455 AAH-1415 AAH-1572 AAH-1470

Solution for this bug

• Ensure the pulp_ansible `/excludes/` work is backported and functioning as expected in pulp_ansible versions used by galaxy_ng
  • galaxy_ng 4.4 uses pulp_ansible 0.10 - backport this work here https://github.com/pulp/pulp_ansible/issues/960
  • galaxy_ng 4.3 uses pulp_ansible 0.7 - this includes a backport but has failed testing https://github.com/pulp/pulp_ansible/issues/959
  • galaxy_ng 4.2 uses pulp_ansible 0.5 - TBD, we have discussed not backporting here
• Update galaxy_ng to use those pulp_ansible versions, so those can go out in the next PAH z-streams