fix: push opened metrics tracked on Android 12

[mrehan27]

fixes: https://github.com/customerio/issues/issues/9483
android sdk changes: customerio/customerio-android#184

Changes

• Requested native SDK to trigger missed lifecycle events so messaging push listener can process notification payload

[github-actions]

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:

<type>: short description of change being made

If your pull request introduces breaking changes to the code, use this format:

<type>!: short description of breaking change

where <type> 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.

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.

[levibostian]

Removed all reviewers since the PR states not to merge it.

Next time, would creating a draft PR work for you? Instead of creating an open PR and ask not to merge it?

I am OK with this, but think that draft PRs would be simpler.

[mrehan27]

@levibostian Draft PRs are for incomplete changes. This PR is complete. The not merging caution was there because it is dependent on Android SDK changes and will not compile without native changes being available. The reviewers were added as the ticket is in testing and I wanted it to be reviewed with native PR, we cannot address PR comments after the testing is complete and native SDK is released.

[Shahroz16]

Looks okay, no changes are needed apart from changing the snapshot to stable. Once we make the changes, we can approve it.

[levibostian]

This comment explains what the code is doing, but it doesn't explain why we are initializing the local SDK reference. What problem this code solves.

A suggestion is that the comment could be modified to answer the question:

Why do we have this code instead of modifying the class from:

private lateinit var customerIO: CustomerIO

to:

private val customerIO = CustomerIO.instance()

[mrehan27]

Added comments to explain it more.

[mrehan27]

@Shahroz16 Updated SDK version to stable release