fix: Rokt User Attribute Mapping Fix

[BrandonStalnaker]

Background

• Investigation found that the mapped userAttributes were being set on the user but when the user is retrieved an forwarded on the kit level the new attributes were not present and since we use user attributes over the passed in attributes it wasn’t being forwarded to rokt correctly. This will be paired to a rokt kit changes to resolve the issue.
• We also decided to add idfa and idfv properties to the FilteredMParticleUser so that this data would be available to rokt (assuming customer allows)

What Has Changed

• Kit configuration values (placementAttributesMapping, hashedEmailUserIdentityType) were being accessed at the wrong nesting level
• Now correctly accesses values through roktKitConfig["as"][key] instead of roktKitConfig[key]
• Added kMPRemoteConfigKitConfigurationKey constant (@"as")
• Added nil check before NSNull check to prevent crashes
• Replaced 6 NSLog calls with MPILogVerbose for consistent SDK logging
• Added exception logging to previously empty @catch block
• Updated existing testGetRoktPlacementAttributesMapping config structure
• Added testGetRoktHashedEmailUserIdentityType
• Added testGetRoktHashedEmailUserIdentityTypeReturnsNilWhenNotConfigured
• Added idfa and idfv properties to FilteredMParticleUser
• Also included a fix for our CI tests so they would run as expected

Checklist

• I have performed a self-review of my own code.
• I have made corresponding changes to the documentation.
• I have added tests that prove my fix is effective or that my feature works.
• I have tested this locally.

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

• Closes https://rokt.atlassian.net/browse/SDKE-692

[nickolas-dimitrakas]

LGTM, one nit