feat: Add Mixpanel Session Replay settings support

[jaissica12]

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

• Added support for Session Replay feature

Testing Plan

• Was this tested locally? If not, explain why.
• {explain how this has been tested, and what, if any, additional testing should be done}

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

• Closes https://go/j/SDKE-663

[rmi22186]

Seems like there's primarily 2 patterns the settings are following here, either if something is a boolean or if it's a number.

I think you can probably do something like

const boolSessionReplaySettings = ['recordHeatmapData', 'autocapture', etc, etc]
const numberSessionReplaySettings = ['recordIdleTimeoutMs', 'recordMaxMs', etc, etc]

boolSessionReplaySettings.forEach(function(boolSetting) {
   if (boolSetting != null) { initOptions[boolSetting] =  boolSetting === 'True'}
})

// something similar for the numberSessionReplaySettings

[jaissica12]

Used dictionaries with { key, mappedKey } since forwarderSettings use camelCase (recordHeatmapData), but Mixpanel's API expects snake_case (record_heatmap_data).

[rmi22186]

I would argue we should just have Mixpanel do the validation on their side and not worry about it on our side.

[jaissica12]

Updated

[alexs-mparticle]

Any reason why you're not checkign != null here?

If this was missed, we could make a simple utility function to make this a little readable.

function hasValue(obj, key) {
    return obj[key] != null;
}

[jaissica12]

I didn't add != null for string settings as it would allow empty strings like recordMaskTextSelector: '' to pass through to Mixpanel, which would break test like "should ignore empty string values for privacy selectors".

[alexs-mparticle]

Extra credit: Maybe we can extract this logic into a utility function to improve readability.

function parseIntSafe(value) {
    var n = parseInt(value, 10);
    return isNaN(n) ? undefined : n;
}