Build: Log benchmark task error

[yannbf]

Closes #

What I did

If the benchmark task errors, it will log a message to mention that is a benchmark error.

Before, it logged like this:

⬇️ Installing local dependencies
> yarn install
➤ YN0000: · Yarn 4.0.1
➤ YN0000: ┌ Resolution step
Test results written to /tmp/storybook/test-results/sandbox.xml
Error running task sandbox:
{
  "errno": -2,
  "code": "ENOENT",
  "syscall": "spawn /bin/sh",
  "path": "/bin/sh",
  "spawnargs": [
    "-c",
    "du -sb ."
  ],
  "cmd": "du -sb ."
}

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

No need.

Documentation

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

Checklist for Maintainers

• 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

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

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 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>