bug: Request are not cached resulting in high network usage

[SeDemal]

Provide environment information

any

Describe the bug

Some queries are not cached but should. This results in an insane amount of queries (This is a 7h span).
This is because the media information for each element needs to be queried separately, resulting in 20 calls every 5 seconds.

To reproduce

Mostly visible using the media request widgets.
Let the page opened for a while then go check your queries in pihole.

Additional information

No response

[manuel-rw]

I think the requests are behaving as designed - we don't know whether the remote data has changed or not - therefore we must fetch all the time.
However, 128K DNS requests do seem extreme - I wonder whether we don't properly cache DNS resolve requests.
@SeDemal can you confirm, that the problem is the amount of DNS requests and not the amount & frequency of HTTP requests? As far as I saw, we cannot reduce the amount of HTTP requests (except the frequency) because the data we need is distributed over multiple API endpoints.
I don't think this is a critical issue and we should not consider this as a blocker for the 1.0 release.
I think that our fetch() simply does not respect any of the TTL nor caches any lookups. See https://www.npmjs.com/package/cacheable-lookup