Process TEStribute results

[uniqueg]

Is your feature request related to a problem? Please describe.

After integrating TEStribute (#16), its results need to be processed. In particular, the resulting list of ranked services should be looped over and the incoming TES request modified such that it uses the recommended DRS object IDs for input files. It is open for discussion how this is to be handled for output files (probably not at all, for the moment). The TES request should then be forwarded to the recommended TES instance.

Describe the solution you'd like

DRS object IDs should be replaced according to TEStributes recommendations in the original TES request and the request should then be forwarded to the recommended TES instance. If any of the services is unavailable, the next combination should be tried.

Describe alternatives you've considered

N/A

Additional context

Depends on #16

Note that TEStribute currently works slightly beyond the GA4GH specs, i.e., it makes an assumption of data repository services that is not warranted by their specification and it amends a property in a model of one endpoint and adds another required endpoint to the TES specs, thus making it depend on specifically tuned TES implementations for now. For this reason, the use of the task distribution logic middleware must be optional (set a switch and necessary config parameters in the config file.

[uniqueg]

This will not be addressed. Alternative task distribution logics are now available and will be refactored as plugins (#160).