build(deps-dev): bump terser from 5.36.0 to 5.46.1 in /console

[dependabot]

Bumps terser from 5.36.0 to 5.46.1.

Changelog

Sourced from terser's changelog.

v5.46.1

• Fix extremely slow (seemed like a freeze) evaluate of method chains
• Parse extremely large floating-point number literals as Infinity
• Remove parens from comma expressions in computed property access (foo[(1, 2)])

v5.46.0

• Add "observedAttributes" domprop (#1652)
• More domprops (mostly Temporal related) suggested in #1652

v5.45.0

• Produce void 0 instead of undefined, which is more safe

v5.44.1

• fix bitwise optimization changing the result of &&, ||
• switches: make sure var is extracted from a deleted default case

v5.44.0

• Support using and await using declarations (#1635)

v5.43.1

• Prevent niche optimizations that would move around block declarations
• Add lhs_constants to CompressOptions type (#1621)

v5.43.0

• Do not wrap callbacks in parentheses (wrap_func_args format option is now false by default)
• Do not inline functions into for loops (for performance reasons)

v5.42.0

• Improved performance in the parse step by adding a fast path for simple identifiers.
• Improved ESTree conversion

v5.41.0

• fixed semicolon insertion between class fields, when the field names are number literals
• keep_numbers format option now works for bigint
• internal: correctly mark accessors' is_generator property
• internal: do not read or assign quote properties without need
• internal: add missing equivalent_to comparison

v5.40.0

• Fix exporting AssignmentExpression (default assign pattern) to ESTree

... (truncated)

Commits

• e186a01 5.46.1
• 04a9625 update changelog
• 1055a1d remove unnecessary properties from AST_Infinity
• 93d03a3 lint
• 8392f62 fix parsing number literals large enough to be perceived as Infinity
• 14d81c5 fix exponentially slower evaluation of chained methods. Closes #1650
• 0ed7a2f no parentheses around comma-expressions (sequences) within computed property ...
• 1550d62 5.46.0
• e5af8ec update changelog
• 0669ea4 add more domprops suggested in #1652
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Thanks for opening this PR! Here are a few tips to help make the review process smooth for everyone.

PR title guidelines

• Use imperative mood: "Fix X" not "Fixed X" or "Fixes X"
• Be specific: "Fix panic in catalog sync when controller restarts" not "Fix bug" or "Update catalog code"
• Prefix with area if helpful: compute: , storage: , adapter: , sql:

Pre-merge checklist

• The PR title is descriptive and will make sense in the git log.
• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).