✨ Update Neodata amp-analytics vendor config with GDPR support and conditional cookie-match

[Ayrton79]

The Neodata vendor config was missing the gdpr=0|1 flag required by the IAB TCF standard, and cookie-match triggers were always active with no way for publishers to control which partners to enable.

Changes:

• Add gdpr=0|1 parameter to the pageview URL, derived from CONSENT_METADATA(gdprApplies) via a gdprAppliesFlag variable in the vars section
• Split the single trackCookieMatch trigger into three separate triggers (trackCmDbm, trackCmAdform, trackCmMediamath), each controlled by a publisher-overridable enableCm* variable that defaults to "" (disabled); publishers opt-in to individual partners from the in-page tag
• Rename requests ADFORM→cmAdform and MEDIAMATH→cmMediamath for naming consistency with cmDbm
• Update vendor-requests.json test fixture and examples/analytics-vendors.amp.html accordingly

[CLAassistant]

All committers have signed the CLA.

[erwinmombay]

heya @Ayrton79 thanks for the contribution. Are you part of NeoData ?

happy to review this once you can get the tests green

[Ayrton79]

heya @Ayrton79 thanks for the contribution. Are you part of NeoData ?

happy to review this once you can get the tests green

Hi @erwinmombay , sorry for the late reply.
Yes, I confirm I am part of NeoData as developer and I'm enabled on https://github.com/neodatagroup organization.

About the tests, i'm checking and it seems something related with CircleCI CLI:
gpg: directory '/home/circleci/.gnupg' created
gpg: keybox '/home/circleci/.gnupg/pubring.kbx' created
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0

Exited with code exit status 2

Are these the errors you are referring to?
Do you have any suggestions for resolving them?

Thanks,
Francesco.

[erwinmombay]

LGTM. if you could get the CL green