Caching changes for URL resolver APIs

[DeepDoge]

• Added back manual memory cache temporarily
• And this time its working as expected
• Also disabled use of browser cache for now
• Thought we are still saying browser to cache it for the future version

[DeepDoge]

Gonna add more commits under this.

[DeepDoge]

What changed?

Since we have 2 different API options(maybe more later) to resolve YouTube IDs and they might have different caching headers or no caching headers at all, I told browser to not cache the API request and handled caching using IndexedDB. (Cache time is 1 day)

Why used IndexedDB?

• If we used force-cache while doing API request they might not expire at all. And API might send bad or invalid or null response that we don't wanna cache forever.
• If we used memory it's not going to be cleaned until browser or extension restarts, so it might grow and grow and grow might cause problems in some cases. And it only lives until the browser or extension restarts.
• If we used LocalStorage and had many caches, we can't select them by expiry date so we need to go through all of the caches and check expiry date. IndexedDB let's us index the caches by expiry date which is a more elegant and a better way to find and delete expired values.