Include security headers in the build and release

[lukaw3d]

No description provided.

[github-actions]

Deployed to Cloudflare Pages

Latest commit:	2ee6a1517516e6efa3b5f3062682f2792ca39137
Status:	✅ Deploy successful!
Preview URL:	https://a6fd0931.oasis-wallet.pages.dev

[buberdds]

Is this meant to be used by devops somewhere in TF scripts?

[lukaw3d]

Possibly

But mainly to make releases actually self contained. When trying to deploy before:

• you had to download the release zip
• find the corresponding release job, and read the build output to find the headers in stdout
  (or risk inconsistency with checking out the released commit and run build locally)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (d21de39) 81.17% compared to head (a83ca8d) 81.17%.

❗ Current head a83ca8d differs from pull request most recent head 2ee6a15. Consider uploading reports for the commit 2ee6a15 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1845   +/-   ##
=======================================
  Coverage   81.17%   81.17%           
=======================================
  Files         192      192           
  Lines        5067     5067           
  Branches      932      932           
=======================================
  Hits         4113     4113           
  Misses        954      954           

Flag	Coverage Δ
cypress	46.20% <ø> (ø)
jest	76.99% <ø> (ø)

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

see 1 file with indirect coverage changes