This change makes all operations necessary to decrypt a notif run atomically and without the risk of corrupoting state after encryption. Unfortunately this means that we might have a network call (call to identity if brand new session creation is necessary) in this critical section. There is a way to enchance this by adopting the approach that we have for web. That is outside of the scope of this diff. and should be handled by separate task. (I will introduce it shortly)

The constructor of ScopedCommMMKVLock will acquire the lock while the destructor will release the lock. This is how we implement finally in C++. So the idea is to create instance of this class and perform a sequence of operations in the scope were the instance is valid.

Interestingly lock and unlock methods are public in Android java wrapper but are not in Objective-C wrapper. However the [[ https://github.com/Tencent/MMKV/blob/v1.3.5/iOS/MMKV/MMKV/libMMKV.mm#L55-L60 | Objective - C wrapper has an instance variable of type mmkv::MMKV ]] so we can use it to access lock and unlock methods.

This is a bit hacky but it is well-known pattern that are using this pattern for CommSecureStore where we redefine EXSecureStore interface with its private methods. This allows us to use them even though they are not publicly available via header file.

Can you add a code comment explaining this?