fix: csp console errors

[Skazitron]

Done

• Removed usabilla -- it's no longer used according to Gloria
• Updated CSP whitelist to prevent the browser from throwing errors (eg. clarity.ms)
• For stuff that can't be whitelisted, they've been put into report only mode. This would include lottiefiles and GTM

QA

• Navigate to the demo or run this bracnh locally.
• Open the browser console.
• Randomly sample a few pages on the website. e.g.
  • https://canonical-com-2807.demos.haus/ceph/support
  • https://canonical-com-2807.demos.haus/public-sector
  • https://canonical-com-2807.demos.haus/openstack
  • https://canonical-com-2807.demos.haus/consulting
  • https://canonical-com-2807.demos.haus/observability
  • https://canonical-com-2807.demos.haus/academy
  • https://canonical-com-2807.demos.haus/data
  • https://canonical-com-2807.demos.haus/microk8s
  • https://canonical-com-2807.demos.haus/juju
  • https://canonical-com-2807.demos.haus/lxd
  • https://canonical-com-2807.demos.haus/legal/data-privacy
  • https://canonical-com-2807.demos.haus/legal/data-privacy/enquiry
  • https://canonical-com-2807.demos.haus/legal/terms-and-policies/contact-us
  • https://canonical-com-2807.demos.haus/legal/confidentiality-agreement
• Ensure CSP violations are in report only mode (grey instead of red).
• NO RED

Issue / Card

https://warthogs.atlassian.net/browse/WD-37313

[webteam-app]

Demo

Jenkins

demos.haus

[mtruj013]

Thanks @Skazitron. There are CSP reports in red flagging usabilla on a few different pages (eg /openstack, /consulting, /observability, /data) is this expected?:

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.82%. Comparing base (fd31c08) to head (1f82573).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2807      +/-   ##
==========================================
- Coverage   74.90%   74.82%   -0.09%     
==========================================
  Files          19       19              
  Lines        2363     2363              
==========================================
- Hits         1770     1768       -2     
- Misses        593      595       +2     

Flag	Coverage Δ
python	74.82% <ø> (-0.09%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Skazitron]

@mtruj013 I've reached out to Gianluigi (from GE/Marketing) to remove the Usabilla from GTM. Since there is nothing else we can do in terms of code, I think we can proceed with the code review.

Update: Gianlugi has confirmed he'll remove Usabilla. Here's the associated ticket for it.

[mtruj013]

Thanks @Skazitron , looks like the usabilla error is gone across the board but now I see the following on all pages:

Confirmed against main that same isn't observed on prod

[Skazitron]

@mtruj013 thanks for the review. Taking another look.

[Skazitron]

@mtruj013 I've deployed it to staging to see if this is just another permission error due to us running the branch locally or if it was caused by our code specifically. I'm leaning towards the former.

[Skazitron]

The 403 errors disappear on staging, so we should be good. Please take another look @mtruj013

[Skazitron]

Flagging so this is reverted before merging.

[mtruj013]

Thanks @Skazitron , LGTM! Leaving +1 with changes for the reversion of the work done to deploy.yaml for qa