• Multiple suffixes for the host URL are tried to support TES APIs hosted at standard and non-standard/legacy locations
• The following suffixes are attempted, in order: /ga4gh/tes/v1 (TES >=0.4), /v1 (TES <0.4), / (i.e., no suffix; for non-standard locations)
• In addition, for the service info endpoint, both the /service-info (TES >=0.5) and /tasks/service-info (TES <0.5) routes are attempted, in that order, with all suffixes, and in that order; i.e., /ga4gh/tes/v1/service-info, /v1/service-info, /service-info, /ga4gh/tes/v1/tasks/service-info, /v1/tasks/service-info, and finally /tasks/service-info
• In case of a 404 response or any requests.exceptions.RequestException, the next path is tried; as soon as a non-404 response is received, no more paths are tried
• If all attempts fail with a request exception, a requests.exceptions.HTTPError is raised, listing the error traces for each path
• If at least one request succeeded, the response is evaluated as before (response.raise_for_status()) and - if no error is raised - returned; no request exceptions are logged in this case
• A new section in the documentation explains the logic and rationale
• Unit tests for new logic was added and existing tests updated, where necessary

Resolves #39
Resolves #40