As a pulp-ansible instance, I want to receive a binary artifact from galaxy-importer when using a git ref

Today when pulp-ansible calls galaxy-importer at upload (i.e. import), pulp-ansible always has the binary artifact, and galaxy-importer returns only the metadata. If pulp-ansible does not have the binary artifact, galaxy-importer should build the binary artifact and return the metadata and the binary artifact

Today pulp-ansible does not call the galaxy-importer on sync, galaxy-importer should support being called on sync. This call should not do open-ended linting that is included when a CollectionVerision is first imported into galaxy_ng. The galaxy-importer should build the binary artifact and return the metadata and the binary artifact.

Upload & Sync workflow, galaxy + pulp_ansible

• Today where upload is a tarball
  • user uploads tarball to server
  • galaxy-importer extracts tarball, returns metadata
  • pulp-ansible stores binary artifact
  • on a PAH sync with Comm Galaxy, PAH syncs and stores binary data
• Future when using a gitref
  • user uploads gitref to server
  • galaxy-importer is called with dir, builds, extracts tarball, returns metadata + binary artifact
  • pulp-ansible stores result depending on config
    • Store just metadata + gitref (this will be config for Comm Galaxy)
    • Store binary artifact (needed for other uses of pulp_ansible like import/export)
  • on a PAH sync with Comm Galaxy
    • For GitRemote ~use_binary_setting=True (the default)
      • If server CV has binary data, pulp_ansible gets metadata + binary data (same as today)
      • If server CV has metadata+gitref, pulp_ansible gets metadata + binary data
        • galaxy-importer is called with dir, builds, extracts tarball, returns metadata + binary artifact
    • For GitRemote ~use_binary_setting=False, pulp_ansible only syncs metadata