throw ESBuild error with correct messages

Problem

Currently if ESBuild running as a child process by CDK cli fails, CDK throws an error Failed to bundle asset..... without the actual error message. The actual error message is printed by the esbuild cli on the stderr which we skip scraping because of wrapping and throwing CDK error in an AmplifyError

Issue number, if available:

Changes

This PR prevents wrapping if the error for instantiating the NodeJSFunction construct is from esbuild and let the cdk_deployer scrape the stderr and throw meaningful message.

Corresponding docs PR, if applicable:

Validation

Checklist

[ ] If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
[ ] If this PR requires a change to the Project Architecture README, I have included that update in this PR.
[ ] If this PR requires a docs update, I have linked to that docs PR above.
[ ] If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

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

aws-amplify / amplify-backend