[Player Model] Fix OSTaskController crashing on LinkedBlockingQueue.poll() on Android 12

[jkasten2]

Description

One Line Summary

Fix rare Android 12 crash with OSTaskController using ConcurrentLinkedQueue.

Details

Android 12 has a bug where ConcurrentLinkedQueue.poll() can return the wrong value. This is rare but results in a few crash reports in OSTaskController, see issue #1761.
To workaround this issue we switched to LinkedBlockingQueue. We have seen reports of crashing in OSTaskController, but we also are also addressing the usages in UserStateSynchronizer.

Related

Issue fixes issue #1761.
ConcurrentLinkedQueue is not used in 5.x.x, so no changes are need there.

Motivation

Crashes are rare, and limited to Android 12, but SDK should cause any crashes.

Scope

Effects some Queues used in OSTaskController and UserStateSynchronizer.

Testing

Unit testing

player-model-main unit tests are not running currently.

Manual testing

Tested on an Android 14 emulator. Ensuring the device subscribes and tags can be added.

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
  • If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
  • Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
• I have reviewed this PR myself, ensuring it meets each checklist item
  • WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

---

This change is