fix: updated json adapter usage to safe parsing

[mrehan27]

Closes: 8311

Changes

• Removed all direct usages of fromJson and fromJsonList from the SDK and replaced with nullable calls
• Since we could not make non nullable parsing methods private because of being inline, added docs to discourage using them directly
• Updated QueueRunner to expect nullable tasks and fail gracefully

[codecov[bot]]

Codecov Report

Merging #140 (9e7c96b) into develop (ddef988) will decrease coverage by 1.26%. The diff coverage is 41.80%.

@@              Coverage Diff              @@
##             develop     #140      +/-   ##
=============================================
- Coverage      58.23%   56.96%   -1.27%     
- Complexity       160      166       +6     
=============================================
  Files             80       87       +7     
  Lines           1707     1787      +80     
  Branches         187      211      +24     
=============================================
+ Hits             994     1018      +24     
- Misses           645      692      +47     
- Partials          68       77       +9     

Impacted Files	Coverage Δ
...messagingpush/CustomerIOPushNotificationHandler.kt	0.00% <0.00%> (ø)
...sagingpush/extensions/ApplicationInfoExtensions.kt	0.00% <0.00%> (ø)
...omer/messagingpush/extensions/ContextExtensions.kt	0.00% <0.00%> (ø)
...tomer/messagingpush/extensions/StringExtensions.kt	0.00% <0.00%> (ø)
...ava/io/customer/sdk/extensions/RandomExtensions.kt	71.42% <ø> (ø)
.../main/java/io/customer/sdk/queue/type/QueueTask.kt	100.00% <ø> (ø)
...va/io/customer/sdk/queue/type/QueueTaskMetadata.kt	100.00% <ø> (ø)
.../src/main/java/io/customer/sdk/util/JsonAdapter.kt	100.00% <ø> (ø)
...src/main/java/io/customer/sdk/queue/QueueRunner.kt	22.50% <13.63%> (-4.53%)	:arrow_down:
...ain/java/io/customer/sdk/di/CustomerIOComponent.kt	54.83% <25.00%> (-0.60%)	:arrow_down:
... and 24 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[ami-oss-ci]

Pull request title looks good 👍!

If this pull request gets merged, it will cause a new release of the software. Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.0.1. This pull request is not a breaking change.

All merged pull requests will eventually get deployed. But some types of pull requests will trigger a deployment (such as features and bug fixes) while some pull requests will wait to get deployed until a later time.

To merge this pull request, add the label Ready to merge to this pull request and I'll merge it for you.

This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...

This project uses a special format for pull requests titles. Don't worry, it's easy! This pull request title should be in this format: ``` : short description of change being made ``` **If your pull request [introduces breaking changes](https://web.archive.org/web/20220725195319/https://nordicapis.com/what-are-breaking-changes-and-how-do-you-avoid-them/)** to the code, use this format: ``` !: short description of breaking change ``` where `` is one of the following: - `feat:` - A feature is being added or modified by this pull request. Use this if you made any changes to any of the features of the project. - `fix:` - A bug is being fixed by this pull request. Use this if you made any fixes to bugs in the project. - `docs:` - This pull request is making documentation changes, only. - `refactor:` - A change was made that doesn't fix a bug or add a feature. - `test:` - Adds missing tests or fixes broken tests. - `style:` - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc) - `perf:` - Changes improve performance of the code. - `build:` - Changes to the build system (maven, npm, gulp, etc) - `ci:` - Changes to the CI build system (Travis, GitHub Actions, Circle, etc) - `chore:` - Other changes to project that don't modify source code or test files. - `revert:` - Reverts a previous commit that was made. ### Examples: ``` feat: edit profile photo refactor!: remove deprecated v1 endpoints build: update npm dependencies style: run formatter ``` Need more examples? Want to learn more about this format? [Check out the official docs](https://www.conventionalcommits.org/). **Note:** If your pull request does multiple things such as adding a feature _and_ makes changes to the CI server _and_ fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.

[github-actions[bot]]

Build available to test Version: rehan-fix-lenient-parsing-SNAPSHOT Repository: https://s01.oss.sonatype.org/content/repositories/snapshots/

[ami-ci]

:tada: This PR is included in version 3.1.0-alpha.1 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

[ami-ci]

:tada: This PR is included in version 3.1.0-beta.1 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

[ami-ci]

:tada: This PR is included in version 3.1.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: