Upgrade body parser dependency (#1530)

### Feature or Bugfix
<!-- please choose -->
- Bugfix


### Detail
- Upgrade `body-parser` dep to avoid vulnerability. Well explained in
[GHSA-qwcr-r2fm-qrc7](GHSA-qwcr-r2fm-qrc7)


### Relates
-
[GHSA-qwcr-r2fm-qrc7](GHSA-qwcr-r2fm-qrc7)

### Security
Please answer the questions below briefly where applicable, or write
`N/A`. Based on
[OWASP 10](https://owasp.org/Top10/en/).

- Does this PR introduce or modify any input fields or queries - this
includes
fetching data from storage outside the application (e.g. a database, an
S3 bucket)?
  - Is the input sanitized?
- What precautions are you taking before deserializing the data you
consume?
  - Is injection prevented by parametrizing queries?
  - Have you ensured no `eval` or similar functions are used?
- Does this PR introduce any functionality or component that requires
authorization?
- How have you ensured it respects the existing AuthN/AuthZ mechanisms?
  - Are you logging failed auth attempts?
- Are you using or adding any cryptographic features?
  - Do you use a standard proven implementations?
  - Are the used keys controlled by the customer? Where are they stored?
- Are you introducing any new policies/roles/users?
  - Have you used the least-privilege principle? How?


By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.

frontend/package.json

@@ -97,7 +97,8 @@
     "express": "4.19.2",
     "ejs": "3.1.10",
     "fast-xml-parser": "4.4.1",
-    "path-to-regexp": "0.1.10"
+    "path-to-regexp": "0.1.10",
+    "body-parser": "^1.20.3"
   },
   "resolutions": {
     "react-redux": "^7.2.6",