Description of problem:
Importing a custom repository with different label but same name causes validation error


Version-Release number of selected component (if applicable): Satellite 6.11


How reproducible:
Always

Steps to Reproduce:
In Upstream Satellite/Org
1. `hammer organization create --name=upstream` (any org name will do)
2. `hammer product create --name=custom --organization=upstream`
3. `hammer repository create --name=repo --content-type=yum --url=https://jlsherrill.fedorapeople.org/fake-repos/needed-errata/ --product=custom --organization=upstream`
4. `hammer repository synchronize --name=repo --product=custom --organization=upstream`
5. Export via `hammer content-export complete repository --name=repo --product=custom --organization=upstream`

Make a note of the path

In the Downstream Satellite/org
1. `hammer organization create --name=downstream` (any org name will do)
2. Create a product with same name but different label -> `hammer product create --name=custom --organization=downstream --label=custom_product`
3. `hammer content-import repository --path=<import path> --organization=downstream`

Expected: 
Successful import with a new custom product and repo added to it

Actual:
Could not import the archive.:
  Validation failed: Name has already been taken for a product in this organization.

Additional Info:
The same error occurs if a custom repository is created with same name but different label