Move special Bid adapter handling from RTD modules into those adapters

[patmmccann]

RTD adapters, particularly those that pre-date standardization of the user.data or site.content.data objects, often have special handling for various bid adapters that don't yet accept standard first party data objects. Discussion in the taxonomy and js committees has suggests this special handling should be moved into those respective bid adapters so that the data controller module can apply.

List of special handlings subject to research.

[ChrisHuie]

List of current RTD modules that have bidder specific logic.

1plusXRTD - Appnexus specific handling
Airgrid - Appnexus specific handling
Captify - Appnexus specific handling

Weboraama - Appnexus, Rubicon, Pubmatic, and SmartAdServer specific logic

Sirdata - CurationID and specific logic for several specific bidders including Xandr, Pubmatic, OpenX, Smart, Rubicon,
IX, Proxistore, Criteo, Triplelift, Avocet, Smaato, and Yahoossp

[patmmccann]

from a conversation with the permutive team on #9555

There are no concerns with an rtd adapter passing information that is private to a bidder, but the js shouldn't need to name bidders to do so. It could take config that looks roughly like this to achieve it:

permutiveRTD: { privateSegments: { what: '_prubicon', who: 'rubicon' where: 'user.ext.data._prubicon'} { who: 'appnexus', what: '_pappnexus', where: 'site.keywords.ext.appnexus' }}

[ydennisy]

@patmmccann I stumbled across this accidentally!

I am about to make some changes to our adapter - is there anything I can do for this yet, I assume from your message above this is a little while out.

[patmmccann]

This issue is approved for prebid 8 enforcement