CORE-64789 Addition of consentPolicies structure to Profile schema

[patnaiku]

The schemas that are impacted by this issue is the profile-union schema.

This will be used as a part of consent initiative implementation in UPS. Once "consent" of the data ingested into the Profile store has been analyzed and evaluated, UPS adds this structure to the merged profile after segmentation and lookup. The downstream services will be able to use the filtered fields from here to take appropriate action.

More on the Consent initiative: https://wiki.corp.adobe.com/display/DMSArchitecture/Consent+Policy+Filter+Logic

Consent in UPS: https://wiki.corp.adobe.com/pages/viewpage.action?spaceKey=DMSArchitecture&title=Consent+Enforcement+Implementation+in+UPS

More about the "consentPolicies" schema: https://wiki.corp.adobe.com/display/DMSArchitecture/Consent+Enforcement+Implementation+Details#ConsentEnforcementImplementationDetails-Additionof%22consentPolicies%22toXDM

Example of consent Policies:

"consentPolicies": { "consentPolicy1": {}, "consentPolicy3": { "email": [ {"id": "[email protected]"}, {"id":"[email protected]"}, {"id":"[email protected]"} ] } }

Protocols followed:

1. ConsentPolicies is map type field where the key is "consent policy id/name" and value is identityMap kind of data type.
2. As consent can be identity specific, keep the value empty if a consent policy evaluates to true for all identities.
3. Don't include consent policies in the profile record that evaluate to false (for all identities).