fix: Update attachLauncher to use options object for integration settings

[alexs-mparticle]

Summary

Adds noFunctional and noTargeting to createLauncher options.

Testing Plan

Pass in noFunctional and noTargeting via the config object in a sample app

[Copilot]

Pull Request Overview

This PR updates the launcher attachment logic to use an options object for integration settings by adding new optional flags "noFunctional" and "noTargeting".

• Added new properties in the test suite to validate the new options.
• Updated the launcher initialization in Rokt-Kit.js to merge the new options when attaching the launcher.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
test/src/tests.js	Added tests to verify that "noFunctional" and "noTargeting" are correctly set when provided, and omitted when not included.
src/Rokt-Kit.js	Updated attachLauncher to use an options object and propagate the integration name along with the new optional flags.

Comments suppressed due to low confidence (1)

src/Rokt-Kit.js:63

• [nitpick] Consider renaming this variable to 'customIntegrationName' to clearly differentiate the raw custom flag value from the processed integration name computed by generateIntegrationName.

var integrationName = customFlags && customFlags['Rokt.integrationName'];

[BrandonStalnaker]

Looks good to my inexperienced eyes (and Cursors)