feat: Implement Google EU Consent

[rmi22186]

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

Implement Braze's EU consent for Google.

The kit should set consent on a Braze user as a custom attribute:

• During kit initialization when a user has set consent previously, and consent mapping is configured in the UI
• When an event is logged, the kit will compare the event's consent state to the most recent user consent state. If it has changed, set the new Braze consent state then send the event. If not, then do not set consent and log the event.

When consent mapping is not configured in the UI, OR a customer does not have consent on it, do not attempt to set consent on the Braze user.

Testing Plan

• Was this tested locally? If not, explain why. - Added unit tests for all the conditions above, and manually tested this in a local app.

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

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

[alexs-mparticle]

I know this is out of scope, but we should add a follow up item to remove the boilerplate tests in favor of the most recent test framework. The boilerplate framework is known to fail silently at times and I would rather we brought Braze in line with the rest of the kits.

[rmi22186]

I'll add this work item to the rollup.test.config.js since I can't add comments to a json file.

https://go.mparticle.com/work/SQDSDKS-6875

[mmustafa-tse]

lgtm overall, just added a couple of suggestions, please ignore if I'm wrong