The ability to easily download artifacts from Pulp given a content pulp href

We need the ability to audit content/packages in Pulp. Ideally, we'd like to iterate through packages in the API and then download them to audit them. The problem we're running into:

• It's hard to correlate a package that's returned in the API with where it might be published at. Once you have its pulp href, you have to go through several steps to find a potential url where it was published.
• It's possible that the package is not even published (we still need to audit these packages).

At first I thought something like having an endpoint like /pulp/api/v3/artifacts/.../download/ would work well (at least for us). However, it looks like there was some work to expose artifacts through a distribution that plugins could use. I don't know if that work could somehow be leveraged for our use case? Pinging @mdellweg in case you have any thoughts.

Start by reading the proposed /pulp/api/v3/artifacts/.../download/ endpoint and the linked pull request 2963 about exposing artifacts through a distribution. Determine the supported behavior for downloading published and unpublished artifacts from a content pulp href; done means the use case has a defined implementation path and corresponding verification.