Cache catalogs and schemas between reloads #296
Description
Now that we have proper EvitaClient implementation with proper caching, we can now implement storing the cache to "disk" (propably browser IndexedDb) so we can load the cache on next evitaLab startup even if the server is not accessible.
This also means, that we need to rework some of the existing tabs that contain user to not wait strictly on server fetch (e.g. GQL Console on schema), we want provide users ability to access their data even if the server is not available.