Implement "GET /service-info"

[uniqueg]

Description

GA4GH API services should come with a service info endpoint that provides essential information required for service discovery and effective usage. Previously, the definition for a service info endpoint was part of each individual API specification. Recently, however, the service info endpoint specification was harmonized and externalized.

Proposed change

• [ ] Add the latest specification for GET /service-info to the repository and include it in the app configuration; ensure that it is added in an order that ensure that the resulting Swagger UI will have the DRS service description - not the service info one
• [ ] Add a dedicated database collection and default service info parameters to the app config, and add the necessary logic to populate the service info once the app starts; see https://github.com/elixir-cloud-aai/trs-filer/pull/40 in the TRS-Filer repository to find out what changes are required; note that the PR also includes a POST /service-info endpoint, which is listed as a separate issue here (see #29)
• [ ] Implement a controller for GET /service-info
• [ ] Add/modify the necessary tests

[sarthakgupta072]

Hey @uniqueg.

The latest specification given here is in OpenAPI 3.0, but drs-filer uses OpenAPI 2.0.

Should I convert it and make a separate file (as done in trs-filer), and give it the name - 20200131.11d2c12.service-info.yaml?

Asking this as I am not using the exact file as it is, but converting it to OpenAPI 2.0 specification.

Please Advice :)