feat: implement rokt launcher into initForwarder

[crisryantan]

Instructions

1. PR target branch should be against development
2. PR title name should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-title-check.yml
3. PR branch prefix should follow this format: https://github.com/mParticle/mparticle-workflows/blob/main/.github/workflows/pr-branch-check-name.yml

Summary

• This PR implements an MVP integration for the Rokt Launcher script via mParticle’s initForwarder function. The changes ensure that the Rokt SDK is loaded the resulting launcher is exposed globally for partner usage.

Testing Plan

• Was this tested locally? If not, explain why.
• This integration was validated locally using the npm run testEndToEnd command. During testing, I confirmed that the Rokt launcher script loads correctly and that the window.Rokt object is present. Additionally, the initForwarder function correctly assigns the launcher to the global scope, ensuring accessibility as expected.

Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)

• Closes https://go.mparticle.com/work/REPLACEME

[rmi22186]

great work getting this going! i have some minor comments. nothing blocking release though.

[rmi22186]

Is there a use case for an mparticle event to be passed to the Rokt SDK for processing? I don't think so. It doesn't hurt to have this, but if Rokt never processes mParticle events, then this can be removed.

Suggested change

	if (window['Rokt'] && eventQueue.length > 0) {
	for (
	var i = 0;
	i < eventQueue.length;
	i++
	) {
	processEvent(eventQueue[i]);
	}
	eventQueue = [];
	}