GPT SRA and Lazy-load fixes.

This beta-release alters the way that GPT functions are called - ensuring that slot definitions and page-level GPT settings are called in the correct order.
These changes allow o-ads to make use of SRA and Google's Lazy-load.

Downgrading webpack as the latest minor version appears to cause build issues.

Merge pull request #559 from Financial-Times/v19.0.1

downgrading webpack

Mostly dev-dependency changes - ensuring that Master branch is in-sync with latest release

This release mostly contains updates to dev-dependencies. Making a release to ensure that master stays in-sync with the latest published release.

[Beta] config module imported from advertising monorepo

v19.0.0-beta.0

ADSDEV-747 use latest ads-config beta

Release v18.3.3

Release v18.3.3

patch: add extension to relative imports to make the code work directly in a browser

Merge pull request #460 from Financial-Times/relative-imports-extension

add extension to relative imports to make the code work directly in a browser

minor: ADSDEV-469 Do not run gpt's enableLazyLoad routine when flag not provided

v18.3.0

Merge pull request #442 from Financial-Times/do_not_run_enable_lazy_l…

Improve accessibility of ad slots

tabindex="-1" and aria-hidden="true" for ad slots

Release v18.1.0:

Exposes GPT Lazy Load functionality.

gpt.enableLazyLoad (optional) <Object> - GPT Lazy Load, where configuration parameters allow customization of lazy loading behaviour.

Default settings are

• fetchMarginPercent: 500, // minimum distance from the current viewport a slot must be before we fetch the ad as a percentage of viewport size. 0 means "when the slot enters the viewport", 100 means "when the ad is 1 viewport away"
• renderMarginPercent: 200, // minimum distance from the current viewport a slot must be before we render an ad. This allows for prefetching the ad, but waiting to render and download other subresources. The value works just like fetchMarginPercent as a percentage of viewport.
• mobileScaling: 2.0 // a multiplier applied to margins on mobile devices. This allows varying margins on mobile vs. desktop. For example, a mobileScaling of 2.0 will multiply all margins by 2 on mobile devices, increasing the minimum distance a slot can be before fetching and rendering.

Release v18.0.0 - Ads Data Refactor

This release refactors o-ads to remove the ads-api calls and instead take all targeting data passed to it via the options object. It cleans up a few other things:

• All targeting will be set through the targeting property of the options object passed to oAds.init()
• removed the ability to validate ads traffic with the moat script. This is now being done in n-ads (https://github.com/Financial-Times/n-ads/pull/77/files#diff-240938b03dfb54ca7c6bfeaa9c3f1a7fR248), or the consuming app by simply inserting the moat script on the page.
• o-ads will not call the ads-api anymore
• npm run test-unit will run jest and qunit tests
• removed ftdomdelegate package as not being used