Self-registration to traefik routing

For now we have a traefik that use strapi API to detect which decidim is hosted where. As it is not updated anymore, we ended up using file.yml in traefik. Now it is really hard to know which route should be kept or not. So we need a more sustainable way of handling routing.

Solution

Instead of writting code, we will use the native traefik Key-Value provider redis. This will be done by:

• having a central redis that store traefik route
• a traefik bound to redis
• decidim-voca that will fire updates on redis regularly to keep routes updated

This means: decidim-voca will be now in power to update it's own routes, and potentially add more states like "in maintenance" "paused", etc.

This will also enable to have a accessible catalog from our CI to do cool things, syncing creating gitlab environments, syncing uptime-kuma etc..