General protection against exceptions that occur on a thread.

[brismithers]

Description

One Line Summary

Update ThreadUtils functions which utilize a thread to always have a high level try/catch. Catching exceptions at the highest level will prevent the exception from being propagated out of the thread and causing the app to crash. Any exception will be logged to the console.

Details

Motivation

An exception within the DSK not causing an app to crash, specifically tracked to #1871 .

Scope

This is handling of exception flows and is broad reaching across the SDK. Exceptions created under a thread will no longer crash the app.

Testing

Unit testing

None

Manual testing

Modified the code running under a thread to throw a RuntimeException and observed the results. Specifically tested for #1871 where opening a URL within an IAM button.

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