fix(engine): Lock in uglify-es version

[trevor-bliss]

PR Checklist

What kind of change does this PR introduce? (add 'x' - [x])

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:
Please check if your PR fulfills the following requirements:

The PR fulfills these requirements:

• Tests for the changes have been added (for bug fixes / features)

• Both unit and integration tests pass

• Docs have been added / updated (for bug fixes / features)

• The PR title follows conventional commit format:
  commit-type(optional scope): commit description.

  Supported commit types: build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test.
  Supported scope: The scope should be the name of the npm package affected (engine, compiler, wire-service, etc.)
  

• More details on LWC semantic commit can be found here.

Other information:

[salesforce-best-lwc-internal]

Benchmark comparison

Base commit: a29cbcd | Target commit: 3ab8916

benchmark	base(a29cbcd)	target(3ab8916)	trend
append-1k.benchmark:benchmark-table/add/1k	360.96 (± 19.81 ms)	462.20 (± 19.81 ms)	👎
clear-1k.benchmark:benchmark-table/clear/1k	56.16 (± 4.53 ms)	74.82 (± 4.53 ms)	👎
create-1k.benchmark:benchmark-table/create/1k	218.16 (± 18.55 ms)	283.70 (± 18.55 ms)	👎
update-10th-1k.benchmark:benchmark-table/update-10th/1k	203.35 (± 17.16 ms)	278.07 (± 17.16 ms)	👎