Refactor code to make more readable check for ability to request notifications permission

More robust check as to whether issue notifications permission request.

1. Replace method overloading with different names.
2. Simplify check for Android OS version.
3. Add comment to explain hardcoded request code for notifications permission.

Add intent-filter for MainActivity to be started from SplashActivity in debug build

Important changes for media files permission and ability to launch MainActivity from SplachActivity

Use compareAndSet since it is safer and cleaner

Use getAndSet() sicne it is safer and cleaner

Reject promise if there is ongoing one already. Check for null promise to avoid NPE.

Bump buildToolsVersion

Mirror iOS behavior on Android 13

I will change JS-visible interface this methods.

In D7058#209899, @ashoat wrote:

Why hasn't this been landed? It's an urgent issue and the diff was accepted on Monday...

In D6921#209900, @ashoat wrote:

Why hasn't this been landed? As mentioned on Monday, we need to create a release with these changes ASAP so we can test the before the end of the month...

Rebase before landing. Add check for code version

Rebase before landing. Extract thread ID key to constant

Rebase before landing

Rebase before landing

Rebase before landing

Rebase before landing

Rebase before landing

Add comment explaining even release pattern

Rebase before landing

Rebase before landing

In D6959#207434, @ashoat wrote:

I considered a solution like this, but I was worried that we would need some synchronization. @marcin, can you share some resources that show that NativeAndroidAccessProvider::runTask is "blocking", ie. it guarantees that the lambda passed to it will finish executing before it returns?

(Passing back with question)

Attach thread to JVM when calling CommSecureStore on Android to avoid JNI crash

In D6959#207341, @ashoat wrote:

Okay, based on that it sounds like your solution is probably better than mine.

2. Let's try to do it without macros if possible (it doesn't seem like we've needed them before, but maybe I'm wrong)

There was a period when we were using macros for this purpose: https://phab.comm.dev/D6416. Now it is refactored not to use macros at the cost of implementing this in Android specific directory. Basically if we want to share a C++, which could potentially cause JNI error, between platforms we have to use macros. If we don't want to use macros we have to make sure that methods called in common C++ that are implemented in Android specific directory are wrapped with NativeAndroidAccessible. In this particular case it is the get method of CommSecureStore that has to be wrapped with NativeAndroidAccessible mirroring what has already been done for set method. I talked to @kamil who wrapped set method with NativeAndroidAccessible. He agreed that similar change should have been done for get.

Rebase

In D6959#207073, @ashoat wrote:

Open to it if there is some benefit over approach in D6958, but would like to see a discussion of tradeoffs.

Post semaphore once and only once. Give lambda a better name

Remove artificial body property

Rebase

Add constant for rescind type indicator

Remove unread constant

Remove rescind handling from AppDelegate.