Snowplow analytics plugin

[oomIRL]

Snowplow search tracking + switching existing tracking over to the analytics plugin.

Search events fire whenever search results are returned, so we get an event for nearly every keystroke.
To get around this there's some logic to only track the most recent search event after a debounce time has elapsed.
This value can be configured via the app-config. Although, right now it's coming from a default value in the analytics module.

I attempted to keep the tracking consistent with the prior method, but I have observed some changes:

• It looks like some pageview events would fire twice occasionally. That's not happening with the backstage events, so I wouldn't be surprised if pageview counts go down as a result.
• Previously, links clicked from techdocs weren't being tracked. Now they are for internal links, but external links aren't generating an event.
• Some of the data attached to click events has changed. The builtin snowplow link tracking would include an array of class names from the clicked element. The Backstage events don't include this information, but do have content info like the button or link text. The Backstage events also include additional information such as entityRefs, routeRefs, pluginIds, but I didn't see anything wildly useful for our analytics.

previous click data

backstage click data

I've got a preview branch up here: https://f5ff48-developer-portal-dev-dprepo-pr-149-f5ff48-dev.apps.silver.devops.gov.bc.ca/
(I dropped the preview for the time being)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[MonicaG]

@oomIRL - thank you for the walk through!

[jenreiher-bcgov]

nothing blocking this, but a few questions! great job :D