feat: add Rokt select placement and refactor sample app, sdk to support new react native version

[thomson-t]

Summary

• chore: Update project structure and add new features
• Added new development scripts and configuration files.
• Introduced new Android and iOS modules for Rokt integration.
• Updated Gradle and Xcode project settings.
• Removed deprecated files and adjusted sample project structure.
• Enhanced TypeScript definitions and added new components for better integration.

Testing Plan

{explain how this has been tested, and what additional testing should be done}

Master Issue

Closes https://go.mparticle.com/work/SQDSDKS-7455

[BrandonStalnaker]

LG from the iOS side

[rmi22186]

i wasn't able to comment in line for some reason, so I'll point to it:

sample/index.js line 180 when you are creating the config using a builder pattern, my comment was:

What do you think about instead of making this a buidler pattern, which isn't done elsewhere in the React code and is very Android-y, that we can either use a factor method, which is more idiomatic, or constructor which isnt idiomatic, but how we have been doing most of the API. https://docs.mparticle.com/developers/client-sdks/react-native/getting-started/#events

ie:
1.

const config = MParticle.Rokt.createRoktConfig("dark", createCacheConfig(3600));

or
2.

const cacheConfig = new CacheConfig(3600, { userId: "123" });
const config = new RoktConfigClass("dark", cacheConfig);

2 seems to match most of the other API, although I prefer 1 and 1 is more idiomatic per cursor

[thomson-t]

2 seems to match most of the other API, although I prefer 1 and 1 is more idiomatic per cursor

Thanks @rmi22186 I've refactored the code.