feat: Add support for Google Click Ids

[alexs-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

• Add support for Google Click Ids

Testing Plan

• Was this tested locally? If not, explain why.
• Run through automated tests. Manually configure sample app to use Integration Capture setting in backend and add relevant gclid, gbraid, wbraid values to query parameters.

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

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

[sonarqubecloud]

Quality Gate failed

Failed conditions
38.2% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

[rmi22186]

LGTM! Making it modular from the beginning really simplifies adding new url parameter click ids.

[samdozor]

looks good.

one higher level concern: we're parsing essentially random data within queryStringParser - who knows what crazy URLs there are out there. I see that we rolled our own parser for when URLSearchParams isn't there (seems like maybe 1-3% of users?). Have you considered having a try/catch to make sure we don't crash if given a totally garbage url?

I looked up the tests for node's internal url.js implementation and there is some wacky stuff it handles, which we do not.

[alexs-mparticle]

@samdozor This is a great callout. I went ahead and created SQDSDKS-6989 so we can work on this.