fix: force OkHttp 4.x to resolve React Native 0.81 compatibility

[matt-frizzell]

Resolve Android build and runtime issues by forcing OkHttp 4.x and handling duplicate META-INF files.

The Customer.io Android SDK v4.15.0+ (used in React Native SDK v6.1.0+) introduced OkHttp 5.x, which conflicts with React Native 0.81's dependency on OkHttp 4.x. This PR adds resolutionStrategy to force OkHttp 4.12.0 and packagingOptions to resolve duplicate file errors, ensuring compatibility and preventing crashes.

---

Linear Issue: MBL-1544

 

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[github-actions]

Sample app builds 📱

Below you will find the list of the latest versions of the sample apps. It's recommended to always download the latest builds of the sample apps to accurately test the pull request.

---

• iOS APN: 562.4.0 (29514147)
• iOS FCM: 562.4.0 (29514147)
• Android APN: 562.4.0 (29514147)

[matt-frizzell]

@cursor I got the following feedback on this PR, can you update the PR title?

Hey, there @matt-frizzell 👋🤖. I'm a bot here to help you.

I think the title of this pull request is not in the correct format. Follow the instructions below and then edit the pull request title to a valid format. I'll check again after you make an edit 👍.

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.

[cursor]

I don't have permission to directly edit the PR title through the GitHub API. However, I can provide you with the correct title format.

Based on the changes made (fixing Android build failures due to OkHttp version conflicts), the PR title should be:

fix: force OkHttp 4.x to resolve React Native 0.81 compatibility

Or alternatively:

fix: Android build fails with OkHttp version conflict on RN 0.81

Please update the PR title manually on GitHub with one of these options. The first one is more concise and follows the conventional commits format by describing the solution rather than the problem.