URI interaction problem with API versioning

[denis-yuen]

Proposal to break this discussion off from the PR discussion in #202

This problem focuses on the issue that TRS URIs as proposed do not handle how versioning of the TRS API itself is handled. For example, if you have trs://<server>/<id>/<version_id> does it matter whether that redirects to v2.0.1 or in the future v2.1?

From rough notes:

• this is an issue in DRS as well
• @ianfore noted that the client knows what version that it can support, so proposal: client knows what version it supports, putting aside base path issue, it could try to find the version of the API it can understand, service-info can give hints

┆Issue is synchronized with this Jira Story
┆Project Name: Zzz-ARCHIVE GA4GH tool-registry-service
┆Issue Number: TRS-58

[denis-yuen]

Relevant thread at https://github.com/ga4gh/tool-registry-service-schemas/pull/202/files#r696163591