Updated TCF specifications based on changes required for TCF v2.2

[HeinzBaumann]

Update the files Tech Lab - Consent string and vendor list formats v2.md and Tech Lab - CMP API v2.md based on the latest policy changes and tech specs. In detail: Update several sections to introduced retention periods for all purposes, removal of legitimate interest for purposes 3 to 6, the introduction of data categories used in conjunction with the purposes, support for legitimate interest claim urls, adding support for localized policy urls. Removed references to v1.1 where that information was no longer required.
Update the GVL list section accordingly: Updated the API specification: Deprecated the API getTCData as well as some other small tweaks. Removed references to v1.1 where that information was no longer required.

[bretg]

@HeinzBaumann - is there a requirements doc? Specifically I'd like to better understand the "data category" concept and whether there's a potential processing implication or if this is just informational to show up in the CMP.

Prebid Server interprets this file and we need to confirm that there aren't updates required beyond the location of the GVL file. Here are the changes gathered from the PR:

• added dataDeclaration array. "An array of positive integers that represent the data categories declared by the vendor". This seems to be related to a requirement that vendors need a "List of Categories of data collected across Purposes".
• added dataRetention object. "an object that contains the data retention for the purpose and specialPurpose declared by the vendor"
• added urls array. "An array of url objects representing language, policy url and legitimate interest url"
• Removal of the policyUrl field.
• certain values are no longer allowed in legIntPurposes

[HeinzBaumann]

@bretg There are Policy updates for all these changes that will be made available. The dataCategory is based of the need to have vendors disclose the type of data the collect/process. This is information for the user to help them make a more informed decision. CMP will need to read and display that information. There is no additional action needed by vendors receiving the TC string.

[achimschloss]

This needs to be updated as discussed

Suggested change

	With the release of TCF v2.2, the policy version has been incremented to version 4. Post 30 September 2023 a TC String with a policy version set to smaller than 4 will be deemed invalid.
	With the release of TCF v2.2, the policy version has been incremented to version 4. Post 30 September 2023 a TC String **created** with a policy version set to smaller than 4 will be deemed invalid. TC Strings with policy version 3 created until 30 September 2023 may still be **returned** by the CMP API post 30 September 2023"

[HeinzBaumann]

I add this change to my next update push. Thanks