CLI: Prebundle boxen to resolve a ESM/CJS incompatibility

[ndelangen]

Closes #

What I did

Users of yarn1 + storybook are running into an issue:

ℹ Storybook build output:
/home/runner/work/addon-visual-tests/addon-visual-tests/build-storybook.log

/home/runner/work/addon-visual-tests/addon-visual-tests/node_modules/boxen/index.js:8
const wrapAnsi = require('wrap-ansi');
                 ^
Error [ERR_REQUIRE_ESM]: require() of ES Module /home/runner/work/addon-visual-tests/addon-visual-tests/node_modules/wrap-ansi/index.js from /home/runner/work/addon-visual-tests/addon-visual-tests/node_modules/boxen/index.js not supported.
Instead change the require of /home/runner/work/addon-visual-tests/addon-visual-tests/node_modules/wrap-ansi/index.js in /home/runner/work/addon-visual-tests/addon-visual-tests/node_modules/boxen/index.js to a dynamic import() which is available in all CommonJS modules.
    at Object.<anonymous> (/home/runner/work/addon-visual-tests/addon-visual-tests/node_modules/boxen/index.js:8:18)
    at Object.<anonymous> (/home/runner/work/addon-visual-tests/addon-visual-tests/node_modules/@storybook/core-server/dist/index.js:47:9068)
    at Object.<anonymous> (/home/runner/work/addon-visual-tests/addon-visual-tests/node_modules/@storybook/cli/dist/generate.js:1:12[55](https://github.com/chromaui/addon-visual-tests/actions/runs/5275056906/jobs/9540144634?pr=8#step:5:56))
    at Object.<anonymous> (/home/runner/work/addon-visual-tests/addon-visual-tests/node_modules/@storybook/cli/bin/index.js:9:1)
    at Object.<anonymous> (/home/runner/work/addon-visual-tests/addon-visual-tests/node_modules/storybook/index.js:3:1) {
  code: 'ERR_REQUIRE_ESM'

see: https://github.com/chromaui/addon-visual-tests/actions/runs/5275056906/jobs/9540144634?pr=8

@tmeasday investigated this and concluded it's related to:
isaacs/jackspeak#5 (comment)
https://github.com/isaacs/jackspeak/blame/main/package.json#L70

How to test

I think we'll have to do a quick alpha release to get this tested in the place where we know it happens.
I think trying to reproduce this in the monorepo will be extremely tedious and fragile, considering it only seems to happen with yarn1.

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]