fix(cli): don't double up on plugin errors and don't show pointless stack trace

[mrgrain]

Improves the error output for plugin loading. We are loosing the green highlight of the plugin name because I doesn't feel right to have formatting inside the error. On the upside, we are loosing stack traces that are irrelevant to the user.

---

Old:

New:

Old:

New:

Also changes all of cli.ts to use the IoHost

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 43.42105% with 43 lines in your changes missing coverage. Please review.

Project coverage is 85.29%. Comparing base (174c2e7) to head (6f17b41).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
packages/aws-cdk/lib/cli/pretty-print-error.ts	13.88%	31 Missing ⚠️
packages/aws-cdk/lib/cli/cli.ts	41.17%	10 Missing ⚠️
packages/aws-cdk/lib/api/plugin/plugin.ts	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #262      +/-   ##
==========================================
+ Coverage   84.92%   85.29%   +0.37%     
==========================================
  Files         219      220       +1     
  Lines       36577    36619      +42     
  Branches     4555     4458      -97     
==========================================
+ Hits        31062    31235     +173     
+ Misses       5371     5285      -86     
+ Partials      144       99      -45     

Flag	Coverage Δ
suite.unit	85.29% <43.42%> (+0.37%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[iliapolo]

What do these do?

[mrgrain]

es2019 is what we had before (the default, but also outdated)

es2022.error adds type support for Error.cause (which is available since Node 16)

[iliapolo]

Are you sure it can only happen because the module cannot be found? Why not use withCause here?

[mrgrain]

As per the docs, this is the only error case:
https://nodejs.org/api/modules.html#requireresolverequest-options

Not using withCause here because the generated Node error contains the Require Stack as part of the error message. See first screenshot. That stack is inherently useless to our users, as it just says tells them that we attempt to load a plugin from the cli code.

I can add some comments around this.