Optimize Embeds away if the non-embeds are already queried

Embeds seem to be useful as they reduce the amount of API calls needed, but at the same time, they can cause issues with the current Caching implementation, as the elements might already be queried, but the embedded API call has not been done yet. So it causes more queries instead of less queries.

Simply stripping the ?embeds=... from the URL when comparing, doesn't work, because the embedded objects might not be queried yet. If there's more than 1 embedded object that it wants to access, it would cause more queries then. So this isn't really a good solution.

Inizia tracciando l’implementazione attuale di Caching e il modo in cui vengono confrontati gli URL delle richieste con ?embeds=.... Definisci il comportamento per gli oggetti non incorporati già interrogati e per più oggetti incorporati, quindi verifica che le chiamate API ridondanti vengano evitate senza saltare i dati incorporati necessari.