Problem Description: 

Product wants to add a certified collection to automate HUB, 

right now there are multiple ways to perform automation on hub API

pulp-squeezer
pulp-cli
galaxy-kit
COP-ah-configuration

Proposed Solution: 

Analyse all the 4 projects, identify the overlaps and proceed with the adoption of one,

the COP collection is the most mature option and if chosen the definition to be done is how HUB engineering team will contribute to the collection maintainability.

Hub Engineers can be added as CODEOWNERS on the COP repository and share the maintenance of the collection.

The collection must be included on galaxy testing pipeline (also QE release pipeline)

We must come with a process for release and how to keep multiple versions of galaxy API supported on the collection (branching?)