[Android] Optimize Secure Storage by Replacing Single Worker Thread with Thread Pool

[farmery]

Problem

Secure storage operations were previously executed on a single worker thread. This becomes a bottleneck when multiple read operations are triggered simultaneously, leading to significant delays due to the synchronous execution on the native side.

Solution

Replaced the single worker thread with a thread pool (using Executors.newCachedThreadPool()). This allows multiple secure storage operations to run concurrently, significantly improving performance when handling simultaneous read/write requests.

Impact

Reduces contention and latency for secure storage operations.
Improves app responsiveness when multiple storage operations are triggered.
No changes in API usage—just an internal optimization for Android.

[farmery]

HI @juliansteenbakker, please can you take a look?🙏🏾

[farmery]

@juliansteenbakker Hii...👀

[juliansteenbakker]

So sorry for the delay, im on vacation till friday, will take a look when i get back!