Description

When a collection is uploaded to PAH with a requirements.yml that includes a community collection, the Dependencies page for that collection contains broken links to the dependency collection by assuming it lives under the "published" repo. It lives under the "community" repo.

(The reverse works: the community collection correctly points to the published repo for the dependent collection.)

PAH About page: Server version 4.4.1

Steps to Reproduce

1. Create 'evanstoner' namespace
2. Upload attached collection
3. Configure 'community' repo in PAH with this requirements.yml: https://gitlab.com/evanstoner/ansible-demo_app/-/blob/master/requirements.yml
4. Go to evanstoner.demo_app collection and view Dependencies page

Actual Behavior

All dependency collections are assumed to live under "published".

Expected Behavior

Dependency link resolution should link to "community" repo when those dependencies are community dependencies. 

Field Checklist:

• Summary
• Description (per template above)
• Component(s)
• Affected Version (what version(s) is this occuring in)
• Priority (Blocker, Critical, High, Medium, Low)
  • assign initial value, but this will be reviewed during triage
• Linked Issue(s) (if relevant; do not use 'subtask of' relationship)