Deploy a TAP service to extract IVOA metadata in Rucio

A fundamental requirement for SRCs will be the ability to expose externally accessible search and retrieve interfaces to data ingested into the distributed data management (DDM) ecosystem. For this purpose, there already exists a standardised set of astronomical interfaces and protocols under the umbrella of the International Virtual Observatory Alliance (IVOA). As such, any DDM solution being considered should ideally be capable of supplying metadata conforming to standards set out by the IVOA.

Through development recently undertaken by Cyan team, Rucio is now capable of storing metadata in standalone, external resources via plugins for e.g. postgresql, mongo. This functionality should enable a service to be deployed that formats and serves this metadata in a way that is compatible with IVOA standards.

As a step towards this goal, an example TAP service (provided by the Tap Library) has been deployed to query mock data. Following on from SP-2825, this now needs to be extended to query a "production" database, connected to the SKAO Rucio prototype. This requires deploying the TAP service into a "production" environment.

As a stretch goal, it would be prudent to consider how the IVOA ObsCore data model can best represent Rucio managed data. Of particular importance is how best to handle replicas - the ObsCore DM defines only a single `access_url`, but a Rucio DID can have many.