Standardize /options endpoints for filter options

[savacano28]

Description

Currently, the /options endpoints are called to retrieve options for different filters (tags, exercise, scenario, injects, assets, tags, etc.), however, these queries can be slow (and are almost duplicated). Should we find a way to standardize these endpoints, either by reducing the scope of the query or by stocking the values in a simple way for retrieval directly from the front end or from a cached database?

[RomuDeuxfois]

I am not sure to understand what's the purpose of this issue.
What do you mean by:

• reducing the scope of the query
• stocking the values in a simple way for retrieval directly from the front end or from a cached database

[savacano28]

Reducing scope: Query with inner joins
Stocking the values..: store, other kind of ddbb (firebase?)