fix: improve delivered metrics

[mrehan27]

closes: https://github.com/customerio/issues/issues/10066

Changes

• CustomerIOFirebaseMessagingReceiver for tracking delivered using C2DM callbacks from GCM
• JvmStatic to methods from CustomerIOFirebaseMessagingService
• Extension function on context to create and retrieve SDK instance in push module
• Refactored PushTrackingUtil to remove redundant code

[github-actions[bot]]

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.

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 #204 (cd38594) into main (3ed104a) will decrease coverage by 0.83%. The diff coverage is 41.37%.

@@             Coverage Diff              @@
##               main     #204      +/-   ##
============================================
- Coverage     63.52%   62.70%   -0.83%     
- Complexity      218      231      +13     
============================================
  Files            91       94       +3     
  Lines          2051     2145      +94     
  Branches        263      281      +18     
============================================
+ Hits           1303     1345      +42     
- Misses          646      691      +45     
- Partials        102      109       +7     

Impacted Files	Coverage Δ
.../customer/messaginginapp/di/DIGraphMessaginIApp.kt	0.00% <0.00%> (ø)
...ustomer/messaginginapp/provider/GistApiProvider.kt	0.00% <0.00%> (ø)
...ssaginginapp/provider/GistInAppMessagesProvider.kt	56.75% <0.00%> (-3.25%)	:arrow_down:
...essagingpush/CustomerIOFirebaseMessagingService.kt	0.00% <0.00%> (ø)
...messagingpush/CustomerIOPushNotificationHandler.kt	0.00% <0.00%> (ø)
...omer/messagingpush/extensions/ContextExtensions.kt	0.00% <0.00%> (ø)
...stomer/sdk/CustomerIOActivityLifecycleCallbacks.kt	7.40% <0.00%> (-4.36%)	:arrow_down:
...java/io/customer/sdk/data/request/DeliveryEvent.kt	0.00% <0.00%> (ø)
sdk/src/main/java/io/customer/sdk/di/DiGraph.kt	100.00% <ø> (ø)
...java/io/customer/sdk/repository/TrackRepository.kt	57.57% <0.00%> (-10.29%)	:arrow_down:
... and 8 more

[github-actions[bot]]

Build available to test Version: fix-gcm-delivered-metrics-SNAPSHOT Repository: https://s01.oss.sonatype.org/content/repositories/snapshots/