Publisher purpose restrictions

[patmmccann]

Tcf strings can require vendors get consent and disallow LI by vendor, eg #14615 has a string doing so. If a vendor cannot rely on LI, tcf control should be aware for purpose 2 enforcement

[dgirardi]

https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/TCFv2/IAB%20Tech%20Lab%20-%20CMP%20API%20v2.md:

    restrictions: {
      '[purpose id]': {
        /**
         * 0 - Not Allowed
         * 1 - Require Consent
         * 2 - Require Legitimate Interest
         */
        '[vendor id]': 1
      }
    }

https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/TCFv2/TCF-Implementation-Guidelines.md#5-encoding-publisher-restrictions-

The vendor registered a purpose as legitimate interest (default legal basis), but also registered this purpose as flexible (i.e. also accepts consent as a legal basis). In this case a "require consent" restriction is needed to signal that the vendor may only process using consent as legal basis.
The vendor registered a purpose as consent (default legal basis), but also registered this purpose as flexible (i.e. also accepts legitimate interest as a legal basis). In this case a "require legitimate interest" restriction is needed to signal that the vendor may only process using legitimate interest as legal basis.

[patmmccann]

publisher committee says this is not breaking and can be fixed in a minor version