chore(csp): Update CSP to allow *.hotjar.io wss://*.hotjar.com

[proeung]

Issue

Fixes -

Description

Changed

• This PR updates both CSPs on Franklin to allow for *.hotjar.io and wss://*.hotjar.com
• This will hopefully address the connection blocking issue that we're seeing on Live/prod.

Design Specs

• Figma Link - N/A

Test URLs

• Before (Changes from main): https://main--merative2--hlxsites.hlx.page/
• After (Changes from this PR): https://chore-csp-for-ws-hotjar--merative2--proeung.hlx.page

Testing Instruction

• No testing instruction is needed.

[aem-code-sync[bot]]

Hello, I'm Franklin Bot and I will run some test suites that validate the page speed. In case there are problems, just click the checkbox below to rerun the respective action.

• [ ] Re-run PSI Checks

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/

[proeung]

@keith-kaplan Thanks for pointing that out. Please see the new commit here - https://github.com/hlxsites/merative2/pull/240/commits/7369543e4edcafa5db2e56c7a15b88aad430fc27

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/		Lighthouse returned error: Something went wrong.

[keith-kaplan]

looks good. I think the lighthouse check failed.

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/

[proeung]

@keith-kaplan Just re-run the psi-check CI.

Also, I noticed that @amol-anand added this performance issue for improving CSP, which is adding to the size of the pages.

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/

[proeung]

@amol-anand @helms-charity Perhaps this is a known issue, but I keep getting inconsistent page performance scores from the helix-psi-check, despite not pushing any new code. Do you know why that is?

[aem-code-sync[bot]]

Page	Scores	Audits	Google
/