feat: changes for react native package

[mrehan27]

This PR adds support for the changes required to align with iOS SDK and make react native package easier to interact

Changes

To fix deep link navigation from notifications, this PR has following changes

• Exposed config in core SDK for following options
  • backgroundQueueMinNumberOfTasks
  • backgroundQueueSecondsDelay
• Added config in in-app module for following options
  • autoTrackPushEvents
• Updated module configurations to enforce builder pattern
• Added option to modify client source for user agent, it now has following options
  • Android (user agent: Customer.io Android Client/2.1.1 (Google Pixel 6; 32) io.customer.remotehabits/1.0)
  • React (user agent: Customer.io ReactNative Client/2.1.1 (Google Pixel 6; 32) io.customer.remotehabits/1.0)
  • Expo (user agent: Customer.io Expo Client/2.1.1 (Google Pixel 6; 32) io.customer.remotehabits/1.0)
  • Other (user agent: Customer.io $value Client/2.1.1 (Google Pixel 6; 32) io.customer.remotehabits/1.0)
• Fixed test cases
• Added kdocs

---

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

• [x] Assign members of your team to review the pull request.
• [x] Wait for pull request status checks to complete. If there are problems, fix them until you see that all status checks are passing.
• [x] Wait until the pull request has been reviewed and approved by a teammate
• [x] 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.1.0. 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 #127 (986799e) into develop (fd7ae28) will increase coverage by 0.31%. The diff coverage is 70.49%.

@@              Coverage Diff              @@
##             develop     #127      +/-   ##
=============================================
+ Coverage      57.94%   58.25%   +0.31%     
- Complexity       156      159       +3     
=============================================
  Files             78       79       +1     
  Lines           1655     1701      +46     
  Branches         184      186       +2     
=============================================
+ Hits             959      991      +32     
- Misses           628      642      +14     
  Partials          68       68              

Impacted Files	Coverage Δ
...o/customer/messagingpush/CustomerIOPushReceiver.kt	2.38% <0.00%> (ø)
...ngpush/lifecycle/MessagingPushLifecycleCallback.kt	21.73% <33.33%> (+2.69%)	:arrow_up:
...src/main/java/io/customer/sdk/data/store/Client.kt	41.66% <41.66%> (ø)
...io/customer/messaginginapp/ModuleMessagingInApp.kt	50.00% <50.00%> (ø)
sdk/src/main/java/io/customer/sdk/CustomerIO.kt	54.86% <50.00%> (-1.45%)	:arrow_down:
...o/customer/messagingpush/ModuleMessagingPushFCM.kt	68.00% <83.33%> (+4.36%)	:arrow_up:
...tomer/messaginginapp/MessagingInAppModuleConfig.kt	100.00% <100.00%> (ø)
...ustomer/messagingpush/MessagingPushModuleConfig.kt	100.00% <100.00%> (ø)
.../src/main/java/io/customer/sdk/CustomerIOConfig.kt	100.00% <100.00%> (ø)
...ain/java/io/customer/sdk/data/store/DeviceStore.kt	96.55% <100.00%> (+0.12%)	:arrow_up:
... and 1 more

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: rehan-feat-react-native-package-SNAPSHOT Repository: https://s01.oss.sonatype.org/content/repositories/snapshots/

[ami-ci]

:tada: This PR is included in version 3.0.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.0.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.0.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: