Enhance Error Handling and Entry Normalization in StorybookNormalizeAngularEntryPlugin

[superhermione]

Closes #

What I did

Description:
This PR introduces several key enhancements to the StorybookNormalizeAngularEntryPlugin to improve its reliability and maintainability within Storybook projects using Angular. The changes focus on robust error handling, support for asynchronous entry configurations, and a streamlined process for merging main and styles entry points to prevent multiple runtime bundles.

Changes:
Error Handling: Added try-catch blocks to capture and log errors when executing entry functions. This ensures that exceptions are handled gracefully and do not disrupt the Webpack build process.
Asynchronous Support: Modified the entry configuration handling to support asynchronous functions by awaiting their results, accommodating configurations that return promises.
Entry Merging: Refined the merging logic for main and styles entries to ensure that only one runtime bundle is generated, preventing the webpack_require.nmd is not a function error.

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

1. Clone the Repository:
   Clone the repository and switch to the branch containing the changes.

2. Install Dependencies:
   Install the necessary dependencies for the project.

3. Build the Project:
   Build the project to ensure that the changes integrate correctly.

4. Run Automated Tests:
   Execute existing automated tests to ensure no existing functionality is broken.

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• [ x] When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts

• [x ] Make sure this PR contains one of the labels below:

  Available labels

  - `cleanup`: Minor cleanup style change. Will not show up in release changelog.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit e0044bc. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 1 target

• nx run-many -t build -c production --parallel=3

---

Sent with 💌 from NxCloud.

[jonniebigodes]

@superhermione, thanks for taking the time to put this pull request together. We appreciate it 🙏 ! Regarding the documentation changes, I'll take a look at it later, as we're on a documentation freeze period. Once that's lifted, I'll be more than glad to follow up with you on it. Sounds good?

Looking forward to hearing from you.

Have a great day.

Stay safe

@valentinpalkovic, I've added the ci do not merge label to this so that we don't accidentally merge it based on what I mentioned regarding the documentation freeze, but feel free to review it from a code standpoint. Will that work for you?