Allow different helmet config to be specified per request path & upgrade helmet to v8.0.0

[t83714]

Allow different helmet config to be specified per request path & upgrade helmet to v8.0.0

When deploying Magda, a user might want to specify different helmet configs for different routes (request path) to allow greater flexibility (e.g. different CSP for different routes).

This ticket introduces a new helm chart config helmetPerPath that allows different config to be specified per request paths. e.g.:

helmetPerPath:
  "routeA/abc": 
    referrerPolicy:
      policy: strict-origin-when-cross-origin

We will also upgrade the helmet to the latest v8.0.0. Other changes related to this:

• users can config content security policy helmet config via key contentSecurityPolicy. Consistent with helmet v8 config reference
• helm chart config key csp is deprecated. User should config content security policy via helmet.contentSecurityPolicy or helmetPerPath.xxx.contentSecurityPolicy.