Remove sensitive data from analytics

[emilk]

I forgot to anonymize the file path in the file:line location of panics, which means we are leaking full paths into our analytics, which can include user names, which is really bad.

We also had the rerun git_branch included (for users building from source), which can also contain sensitive stuff.

All affected analytics event have been deleted, and new ones will be filtered.

A patch-release is coming in

• Release 0.3.1 #1574

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct

[nikolausWest]

Summary of issue

• For users that built Rerun from source, analytics events would include the current git branch name (of the rerun repository)
• For users that experienced a panic, the file path and line number (of where the panic happened in rerun's code) was included in the analytics event. These paths weren't properly anonymized and could therefore potentially include identifiable information in some case.

Resolution

In addition to fixing the code we have made sure to scrub all analytics databases of any traces of the leaked non-anonymized paths and git branch names. We have also set up server side filters to drop the affected data before ingestion to avoid any of this data getting to our analytics databases in the future.

• All events related to anonymous user id's that were associated with one or more panic events with non-anonymized file paths have been deleted
• All events related to anonymous user id's that were associated with a branch name that wasn't created by the core Rerun team have been deleted
• Add server-side event filtering to drop any similarly effected data in the future (coming in from version 0.3.0)