[BP-1.20][FLINK-36740] [WebFrontend] Update frontend dependencies to address vulnerabilities

[mehdid93]

What is the purpose of the change

This PR backport the changes done of the PR made by me in (#25718) in master for version 1.20.X to be used in dependencies upgrade and vulnerabilities fixes.

Brief change log

• Update of the dependencies

Verifying this change

Please make sure both new and modified tests in this PR follow the conventions for tests defined in our code quality guide.

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): yes
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[flinkbot]

CI report:

• d19d251 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[davidradl]

I suggest a comment detailing what the shell script does, why is would be useful and when to run it.

[davidradl]

we should say npm dependancies I think.

[afedulov]

@flinkbot run azure

[afedulov]

@flinkbot run azure

[davidradl]

waiting for a clean CI then will approve

[afedulov]

@davidradl are you OK with merging?

[afedulov]

@mehdid93 I already rebased your branch, CI is green.

[mehdid93]

@afedulov Thanks a lot for rebasing and merging the PRs. I've rebased because when I've opened this PR there was some conflicts shown in github with package.json and package-lock.json after the merge of the previous PR (#25829) and this one have conflicts in package-lock.json and package.json

[afedulov]

Ah, OK, thanks for the clarification. Does that mean we are deviating from the original commit from master? If so, please add a note in the PR description what exactly got changed.

[mehdid93]

@afedulov No, we're not deviating from the original commit, it's the same thing, but since package and package-lock were affected in both PRs, the conflicts were resolved by taking package-lock and package from the original commit (this PR), since they're the most recent state.