Rethink feed detail caching for authenticated users

[Alessandro100]

For authenticated feed detail inquiries we currently cache the API response on the Next server for 10 minutes. This is not very efficient as this cache will only affect that specific authenticated user and to store it on the server only serves that user. Options

1. Implement a client-side cache using SWR so the cache isn't stored in the server and is user specific. With this method we can explore ways to invalidate the client-side cache using our revalidate endpoint
2. Think about a specific role system ex: not authenticated, authenticated, authenticated mobilitydata. This would allow us to cache static pages for each of these roles. This would require longer term vision of how we will allow users to access the feed detail page.