Background

• Create an endpoint to list the tempo stacks and the tenants included in each one of them
• Create a endpoint to proxy query requests from the plugin to tempo stacks based

Outcomes

The plugin front-end can read the list of tempo stacks of the plugin via a REST API, so the tempo stacks can be listed.

A REST API is created so

• making a call to `{plugin-backend-location}/tempo-stacks` will return the list of tempo stacks in the cluster
• making a call to `{plugin-backend-location}/proxy/{tempo-stack-name}` will proxy queries to the tempo stack service