feat: Handle emailsha256 and other before sending attributes to Rokt Kit

[Mansi-mParticle]

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 includes logic to handle emailsha256 and other before passing attributes to the Rokt Kit:
  If emailsha256 is present, remove both email and other from the attributes.
  If other is present (and emailsha256 is not), map other to emailsha256, then remove both email and other.

Testing Plan

• Was this tested locally? If not, explain why.
• Tested with sample app

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

• Closes https://go.mparticle.com/work/SQDSDKS-7556

[rmi22186]

looks good...how about some tests that cover the following:

• If email identity exists on the user, and emailsha256 attribute is passed to selectPlacements, do not send email attribute to the selectPlacements call.
• if email identity and other identity exist on the user, only pass emailsha256 attribute with the value from other identity

I think these would go in the kit, not core

[BrandonStalnaker]

Update your addIdentityAttributes method to add the other identity as the "emailsha256" key instead. That way you don't overwrite the other attribute if its passed in.

[BrandonStalnaker]

Just a couple minor things