Experimental engaged session switch

[ukutaht]

Background

An experiment to see how it would look like to add a 'engaged sessions only' filter to deal with bot traffic. An engaged session is defined as a session with at least one engagement event.

This is intentionally the smallest way to test this in production. It is meant to be easily revertable. If the experiment is a success in that the filter:

• Helps clean up dashboards with spam
• Does not exclude too much real human traffic

Then the plan is to revert this commit and think about how to build this properly. Currently it ignores many considerations including realtime data, imported data, and historical data before engagement events were even added.

Changes

For superadmins only, adds a UI switch that always applies a [:has_done, [:is, "event:name", ["engagement"]] filter to all API requests. Does not apply to the current visitors number and when enabled, imported data is inaccessible due to backend rules.

Tests

• Automated tests have been added

Changelog

• This PR does not make a user-facing change (experiment for super-admins only)

Documentation

• This change does not need a documentation update

Dark mode

• The UI has been tested both in dark and light mode

[github-actions]

Preview environment👷🏼‍♀️🏗️
PR-6610

[aerosol]

Interesting idea, let's see how it behaves