Add tracking to disco pane

[muffinresearch]

Fixes mozilla/addons#5626

• Adds tracking lib
• Uses async setup as per GA docs
• Adds CSP config (we might need more than this if beacons go to other hosts).
• preventDefault added (I was seeing 2 beacons fired) this probably meant installs were kicked off twice too.
• adds the install and uninstall events.

[coveralls]

Coverage remained the same at 100.0% when pulling f5b040c on muffinresearch:add-tracking-to-disco into c254967 on mozilla:master.

[coveralls]

Coverage remained the same at 100.0% when pulling 5b439f4 on muffinresearch:add-tracking-to-disco into c254967 on mozilla:master.

[mstriemer]

preventDefault added (I was seeing 2 beacons fired) this probably meant installs were kicked off twice too.

I think installed only happened once since we would change the state and the second time it would do nothing. This is what I noticed with themes though but I didn't dig into it then.

[mstriemer]

I presume GA is smart enough to separate the data based on origin so we only need the one ID for dev, stage and production?

[mstriemer]

I think destructuring should have spaces so constructor({ trackingId, trackingEnabled, _log = log } = {}) {

[muffinresearch]

I presume GA is smart enough to separate the data based on origin so we only need the one ID for dev, stage and production?

Yep - you can work out stats by host. Addons-server only has one id set directly in JS.

[mstriemer]

I'd say destructuring format again here.

[mstriemer]

r+wc

[coveralls]

Coverage remained the same at 100.0% when pulling 229343c on muffinresearch:add-tracking-to-disco into 4a08338 on mozilla:master.

[coveralls]

Coverage remained the same at 100.0% when pulling 7e25dd8 on muffinresearch:add-tracking-to-disco into 4a08338 on mozilla:master.