Sessions view

[EDsCODE]

Changes

• implement Sessions View #882

Todo:

• paginated
• surface all related properties to the person in session
  - [ ] add migrations to create materialized table for prexisting data
• red indicator for currently in progress

Checklist

• All querysets/queries filter by Team (if applicable)
• Backend tests (if applicable)
• Cypress E2E tests (if applicable)

[EDsCODE]

@timgl This is ready for another look! I ended up not using materialized views or any database specific optimization strategy because it seemed overkill to manage. I figured out a format of the feature that makes the queries really light. Instead of trying to compute the entire sessions table, I've setup the page to work by day. This actually makes the browsing experience better because you can actually scroll to a specific day and find what people were up to. This way, the queries can be extremely precise and quick.

However, the one inconvenience happens when you reach the end of a specific day. There is a way to fix this but it would lead to another problem where sparsely logged events would make pagination on this page really weird. LMK what you think!

[timgl]

When scrolling through this, I really found myself wanting to filter this just by people with email addresses. Could be another ticket though!

Couple small things below

[timgl]

Mergy conflicts

[mariusandra]

I found one thing: when you change the pagination, the "order" still starts from "1", even if it should probably start from 51: