Solve critical vulnerability of Presto UI from @babel/traverse npm package

[yhwang]

Ref: #21319

Description

Update @babel and related packages to newer versions to solve the critical vulnerability issue reported by yarn audit: GHSA-67hx-6x53-jw92

Motivation and Context

The critical vulnerability issue reported by yarn audit may impact servers that run the babel to compile the Presto UI code or developers' machines. Although there is no path.evaluate() or path.evaluateTruthy() in the current code base, it's good to fix it.

Impact

Most of the JS files are not changed, except query.js.

Test Plan

Manually run the Presto UI and verify the query page.

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

General Changes
* Update Babel and related npm packages to solve critical vulnerability: https://github.com/advisories/GHSA-67hx-6x53-jw92
  The Babel packages are used to generate the JavaScript files for Presto UI. The update prevents the build servers
  or developers' machines from running arbitrary code while building the JavaScript files.

[yhwang]

Below, it's a screenshot of the query page, I don't see any issue of this page.

[yhwang]

Here is another screenshot which has a successful query:

[skairali]

This is a good change and required one from security perspective.

[steveburnett]

If this is a "critical vulnerability" as described in the title, consider adding a release note to this PR for the Security section of the next release notes.

[yhwang]

@steveburnett thanks for the feedback. update the description of this PR to include the release node.