refactor(csp): remove unsafe-eval in dev mode

[clarkdo]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Follow up #7305 and #7454, now we won't have any eval code if csp is enabled without explicit unsafe-eval config, so we can remove unsafe-eval in dev mode now which will make csp in dev and prod more consistent.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly. (PR: #)
• I have added tests to cover my changes (if not applicable, please state why)
• All new and existing tests are passing.

[codecov-commenter]

Codecov Report

Merging #7659 into dev will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##              dev    #7659   +/-   ##
=======================================
  Coverage   70.18%   70.18%           
=======================================
  Files          88       88           
  Lines        3756     3756           
  Branches     1020     1019    -1     
=======================================
  Hits         2636     2636           
  Misses        911      911           
  Partials      209      209           

Flag	Coverage Δ
#unittests	70.18% <100.00%> (ø)

Impacted Files	Coverage Δ
packages/server/src/middleware/nuxt.js	97.53% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d4363d4...06fff1f. Read the comment docs.