feat: Include consent query parameters for cookie sync

[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

• If a consent string is not appended to GMP Cookie Syncs, Google will exclude these users from audiences. TCF (Transparency and Consent Framework) has specific implementation instructions that all cookie sync customers follow in order to include if someone has or has not consented
• All Consent Management Platforms (such as OneTrust), are required to implement a function on window.__tcfapi to return TCF strings which contains what a user has/has not consented. This gets appended to the end of a cookie sync.
• We call the API using getInAppTCData, which then returns a tcData object, and we only need the keys gdprApplies and tcString

Testing Plan

• Was this tested locally? If not, explain why.
  Added unit tests

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

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

[sonarqubecloud]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.5% Duplication on New Code

See analysis details on SonarQube Cloud