Angular: Support storybook configuration for projects with only angular Library

[ThibaudAV]

Issue: 🤷‍♂️

If the use of the native ng builder for sb is well adopted. It solves several issues.
I think, it should be released officially in storybook 7. because it is a major change 🤔

if you're reading this and you're interested, I'd love some feedback on this :)

What I did

Previous PR : #15061

Allows to use sotrybook without relying on an existing configuration (angular.json artifact).
Can be used for projects with only ng library

Only tsConfig is required
ex :

    "without-browser-target": {
      "root": "",
      "projectType": "library",
      "architect": {
        "storybook": {
          "builder": "@storybook/angular:start-storybook",
          "options": {
            "tsConfig": "src/tsconfig.app.json"
          }
        },
        "build-storybook": {
          "builder": "@storybook/angular:build-storybook",
          "options": {
            "tsConfig": "src/tsconfig.app.json"
          }
        }
      }

How to test

• Is this testable with Jest or Chromatic screenshots? Yes
• Does this need a new example in the kitchen sink apps? Yes
• Does this need an update to the documentation? Not Yet, for storybook 7.0 🤞

If your answer is yes to any of these, please make sure to include it in your PR.

[nx-cloud]

Nx Cloud Report

CI ran the following commands for commit 1604b61. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status	Command
	nx run-many --target=prepare --all --parallel --max-parallel=15

---

Sent with 💌 from NxCloud.

[shilman]

Looking good @ThibaudAV ! Are there any documentation updates needed here?

[ThibaudAV]

Looking good @ThibaudAV ! Are there any documentation updates needed here?

@shilman I think we need to add some documentation on this. But I think I'll do it in another PR when the feature is more complete.
And for sb v 7 🤷‍♂️

[shilman]

Thanks @ThibaudAV !! Looking great 😍

[shilman]

@ThibaudAV OOPS I missed the comment about being a major change ... Should I revert it in 6.4? Or can we figure out how to make it a non-breaking change? For example, put it behind a feature flag?

[maxisam]

Can't wait to see this release officially! I hope we can use it in 6.4!

[shilman]

@maxisam you can try it out today using:

npx sb@next upgrade --prerelease