GPP Control module: Handle usnat version 2 strings

[patmmccann]

https://iabtechlab.com/gpp-update-important-changes-to-inform-your-data-privacy-roadmap/

The breaking changes exist in two fields of the string:

SensitiveDataProcessing field introduces several new categories (13-16)
KnownChildConsents field introduces new age range

https://github.com/InteractiveAdvertisingBureau/Global-Privacy-Platform/commits/main/Sections/US-National/IAB%20Privacy%E2%80%99s%20Multi-State%20Privacy%20Agreement%20(MSPA)%20US%20National%20Technical%20Specification.md

We are not yet aware of any version two implementations. https://www.gppdecoder.com/usnat.html is on version 1

[patmmccann]

Here are the new logic for knownChild, if we see a 1 in the third element of the array, we opt out the user.

[patmmccann]

@bretg the the new requirements for age seem simple, the new sensitive categories not so much, particularly with Meredith's advice re transgender diverging from sexual orientation. We'd welcome your proposal.

[bretg]

Ok, updated the analysis sheet and the normalization issue for SIDs 13-22.

Here's a proposal for what needs to change in the default processing logic described in
https://docs.prebid.org/features/mspa-usnat.html#interpreting-usnat-strings

1. Add the following condition to the block defined in syncUser

KnownChildSensitiveDataConsents[3]=1 OR     # no consent for new KnownChild ages 16-17

2. Add the following condition to the block defined in transmitUfpd

KnownChildSensitiveDataConsents[3]=1 OR     # no consent for new KnownChild ages 16-17

3. Update these conditions in transmitUfpd:

...
SensitiveDataProcessing[1-7,9-12]=2) --> SensitiveDataProcessing[1-7,9-16]=2)
...
SensitiveDataProcessing[1-5,11]=1 OR --> SensitiveDataProcessing[1-5,11,13,15]=1 OR
...
SensitiveDataProcessing[6,7,9,10,12]=1 OR --> SensitiveDataProcessing[6,7,9,10,12,14,16]=1
SensitiveDataProcessing[6,7,9,10,12]=2 OR --> SensitiveDataProcessing[6,7,9,10,12,14,16]=2

4. Add the following condition to the block defined in transmitPreciseGeo

KnownChildSensitiveDataConsents[3]=1 OR     # no consent for new KnownChild ages 16-17