@nx/storybook/plugin should use its own executor in non-angular cases

[comp615]

Current Behavior

Currently, the @nx/storybook package provides executors for building and serving storybook.

However, when one uses the @nx/storybook/plugin to generate inferred tasks, unless the angular framework is detected, these tasks are generated running the storybook CLI directly.

Code Reference

Expected Behavior

The plugin should reference its own executor when creating the tasks, this would provide more consistency and flexibility between the angular and standard implementation, as well as CLI/options compatibility. Currently it's very confusing to decide if we want the provided executor or the inferred tasks since they are mutually exclusive (it's impossible to merge a different executor over the inferred task in NX by design)

GitHub Repo

No response

Steps to Reproduce

1. Open a storybook based package
2. run nx show project
3. Observe the chosen executor

Nx Report

Node           : 22.9.0
OS             : darwin-arm64
Native Target  : aarch64-macos
pnpm           : 9.11.0

nx                 : 20.0.1
@nx/js             : 20.0.1
@nx/jest           : 20.0.1
@nx/eslint         : 20.0.1
@nx/workspace      : 20.0.1
@nx/cypress        : 20.0.1
@nx/devkit         : 20.0.1
@nx/eslint-plugin  : 20.0.1
@nx/plugin         : 20.0.1
@nx/react          : 20.0.1
@nx/storybook      : 20.0.1
@nx/vite           : 20.0.1
@nx/web            : 20.0.1
typescript         : 5.5.4
---------------------------------------
Registered Plugins:
@nx/vite/plugin
@nx/storybook/plugin

Failure Logs

Package Manager Version

No response

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

No response

[AgentEnder]

This is intended - inferred tasks prefer raw commands if possible to make things easier to configure for folks that are more familiar with the tool (storybook in this case) and less familiar with Nx. This is a bit of a weird area where it is possible to use the command for almost all of them, but the angular case isn't quite ready yet.