First party cookie support for capping

Following incoming events connected with 3rd party cookies and their unstable future - we enable 1st party cookie support for capping. It's being enabled from the config script level. To make it work you need to use below parameteres:

fpc - this parameter enables / disables first party cookie support with below values:

• "auto" - first party capping will be enabled when ado.js will detect that web browser is not handling 3rd party cookies only (checked every 8 hours);
• "false" - first party capping is disabled;

defaultServer - emitter domain according to which 3rd party cookie support in web browser will be tested.

cookieDomain - (not obligatory) domain for which first party cookie will be set. Possible options:

• "SLD" (Second Level Domain) - cookie will be set for main domain (e.g. on sport.example.com cookie will be set for example.com so this way the cookie will be for both - example.com and sport.example.com). 
  WARNING! This setting cannot be used if you have second level domain which doesn't belong to you, e.g. in example.com.pl domain "com.pl" part is SLD, in example.co.uk "co.uk" part is SLD and so on. In this case cookie won't be set and capping won't work.
• "HOC" (Host Only Cookie) - default value. This will set cookie separately for each domain and subdomain.
• domain - you can also set a specific domain for which cookie will be set, e.g. sub.example.com. This will make capping work for sub.example.com but also for each subdomain like sub2.sub.example.com.
  WARNING! The domain you will set here have to be at least a part of domain for which ado.js library is being executed.

example configuration:

Additional information:

• Capping works per publisher domain and is saved in 1st party cookie.
• Cookie is set in domain calculated by ado.js, based on "cookieDomain" field from configuration script.
  
• Works for ES6 supported web browsers only (including Promise and Fetch).
• Capping works for impression / impression attempts in current state.
• Requires ado.js. Not supported by aomini.
• First party cookie capping won't work for ado.js executed in 3rd party frame (like iframe or AMP codes).

adocean capping