Vendor part of Sentry-SDK for scrubbing requests errors

[thesujai]

Summary

1. vendors the sentry scrubber.py to match our own needs.
2. Update to new Core API
3. Address some suggestions from GSoC: Distributed error reporting #12489

References

Fixes #13395

Reviewer guidance

NA

[github-actions]

Build Artifacts

[thesujai]

@rtibbles cc

[rtibbles]

Generally, this is looking good to me. One small bit of cleanup where I think we can just use the KDS breakpoints.

I think we need to rebase the feature branch again, but easier to do that after this has been merged.

[rtibbles]

I think instead of adding this separate screenBreakpoint utility here, we can use the KDS breakpoints instead.

Can probably just import:

import useKResponsiveWindow from 'kolibri-design-system/lib/composables/useKResponsiveWindow';

then in the function body do:

const { windowBreakpoint } = useKResponsiveWindow();

Just need to make sure to then reference windowBreakpoint.value when passing it into the context object.

[thesujai]

I tried and had a problem:

windowBreakpoint.value is always null when i try to call it from kolibri/plugins/error_reports/assets/src/utils.js

Here is what I am doing

import useKResponsiveWindow from 'kolibri-design-system/lib/composables/useKResponsiveWindow';

const {windowBreakpoint} = useKResponsiveWindow();
    

console.log('windowBreakpoint', JSON.stringify(windowBreakpoint));

I see this in console:

windowBreakpoint {"value":null}

[rtibbles]

Hrm, this is probably because we're using it outside a component, so the tracking isn't working.

[thesujai]

So is there a workaround for this?

[rtibbles]

I think it's probably easiest just to copy the logic and read the values when we report an error.

Can just copy the array here: https://github.com/learningequality/kolibri-design-system/blob/develop/lib/composables/useKResponsiveWindow/index.js#L67

And then compare the window width to get the breakpoint.

[rtibbles]

If we're using the KDS breakpoints, then we can set this as a non-negative integer.

[rtibbles]

This is looking good to go, I'm going to give it a manual run through tomorrow to be sure, but nothing immediately jumping out to me!

[rtibbles]

It seems like we don't actually use this function anywhere? May be simpler to just merge the DEFAULT_PII_DENYLIST above into the other list, and then remove this function?

[thesujai]

Thanks! done