fix(types): provide simplistic storage interfaces

[wodCZ]

Provide an interface for each wrapper, which captures the required subset of the actual expected storage.
Also, added support for MMKV storage v0.5.7+ in the process.

fix #426, #431

[wodCZ]

The web example with LocalStorageWrapper now works fine. I haven't tested the other storages, but since the change is the same for all the providers, I expect it'll fix all of them.

I experimented with building upon the generics, which could actually perform the type-check against the provided storage, but I failed 😔 . Maybe someone else could attempt, as the types are practically blind now.

[wtrocki]

Left comments on other PR..What is the relation between them

[wodCZ]

@wtrocki uploaded the changes as discussed in #437

This also includes the MMKV compatibility fix, since I needed to match the actual interface (the change is already bringing fruits :D ).

I haven't tested this, so please if anyone can give it a try - I'll not be able to test at least until tomorrow, but at the same time, I didn't want to stall this. LocalStorage should be simple to test using the web example, the I'd like to test at least LocalForage since it's slightly unusual & AsyncStorage as a popular RN choice.

[wtrocki]

Ok to merge this? Does that compile for web example?
We can do prerelease for testing purposes.

[wodCZ]

Sorry, just got to test this.

Unfortunately, this doesn't fix the issue 😢 .

The problem is in the generics - we only type-check what the storage wrapper can accept. But the rest of the persistor is still passing around PersistedData<NormalizedCacheObject>, which of course is not assignable to string the storage accepts.

What needs to be done is that based on the serialize?: boolean option the CachePersistor must switch between "I'm passing around PersistedData<NormalizedCacheObject>" vs "I'm passing around string".

I've updated most of the types now to carry the information, but I'm missing some bit somewhere...

Not ready to merge, sorry.

[wodCZ]

Ok, I think I fixed it.

Tested both web and react-native examples and all seems to be working.

We can do prerelease for testing purposes.

@wtrocki Please do if you approve my changes - I'm ok with merging this now.

[wtrocki]

Verified web only. Looks like it is working