fix: upgrade dependencies

[levibostian]

QA:

• Test this PR with RH builds pr.58
• This PR updates major libraries that our SDK depends on to operate successfully. For us to be most confident that our SDK operates as expected, simply testing that a push notification can be received (simple or rich) and an event is tracked is sufficient.

Closes: https://github.com/customerio/issues/issues/8330

Complete each step to get your pull request merged in. Learn more about the workflow this project uses.

• [ ] Assign members of your team to review the pull request.
• [ ] Wait for pull request status checks to complete. If there are problems, fix them until you see that all status checks are passing.
• [ ] Wait until the pull request has been reviewed and approved by a teammate
• [ ] After pull request is approved, and you determine it's ready add the label "Ready to merge" to the pull request and it will automatically be merged.

[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.

[codecov[bot]]

Codecov Report

Merging #146 (7493da4) into develop (145c047) will decrease coverage by 0.15%. The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop     #146      +/-   ##
=============================================
- Coverage      60.89%   60.73%   -0.16%     
  Complexity       187      187              
=============================================
  Files             90       90              
  Lines           1923     1923              
  Branches         237      239       +2     
=============================================
- Hits            1171     1168       -3     
  Misses           668      668              
- Partials          84       87       +3     

Impacted Files	Coverage Δ
...epository/preference/SharedPreferenceRepository.kt	97.22% <0.00%> (-2.78%)	:arrow_down:
.../src/main/java/io/customer/sdk/util/SimpleTimer.kt	74.41% <0.00%> (-2.33%)	:arrow_down:
...main/java/io/customer/sdk/api/HttpRequestRunner.kt	77.19% <0.00%> (-1.76%)	:arrow_down:
...messagingpush/CustomerIOPushNotificationHandler.kt	0.00% <0.00%> (ø)

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

[github-actions[bot]]

Build available to test Version: levi-update-dependencies-SNAPSHOT Repository: https://s01.oss.sonatype.org/content/repositories/snapshots/

[levibostian]

We can test this PR with RH builds pr.58. Added QA instructions to description of PR and moved status of PR to in QA.

[ami-ci]

:tada: This PR is included in version 3.3.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.3.0-beta.1 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

[github-actions[bot]]

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

The release is available on GitHub release

Your semantic-release bot :package::rocket: