Controls: Fix esm is not defined error with built Storybook

[gaetanmaisse]

Issue: #15773

What I did

I reverted #14394 because it looks like it's the commits that introduced the esm is not defined error. It will need some deeper investigation.

How to test

• e2e ci steps should be back to 🟢

[nx-cloud]

Nx Cloud Report

CI ran the following commands for commit 5f589a2. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status	Command
	nx run-many --target=prepare --all --parallel --max-parallel=15

---

Sent with 💌 from NxCloud.

[gaetanmaisse]

Angular related E2E tests are still failing but for another reason, addon-controls doesn't consider user as an arg 🤔 (with a def value)

[gaetanmaisse]

@shilman @stevensacks was the unbox the value to simplify the code commit mainly cosmetic or was there a deep reason for that changes?

[shilman]

@gaetanmaisse the old boxing/unboxing code was a hack because when you try to use React's useState with a function value it breaks unless you either (1) box it, or (2) do what @stevensacks proposed which is simpler and slightly more efficient. However, until we have a fix for the problem at hand (which maybe has something to do with how the fix interacts with our webpack settings? or maybe just isn't quite right?) we should revert since the bug is a blocker and getting in the way of people using the alphas.