fix(storybook): return baseUrl from storybook and use in cypress

[mandarini]

Pass the port and the baseUrl from the Storybook devServer to the cypress executor.

Why this schema?

Reason why we are using the info?: { port: number; baseUrl?: string }; schema:

The @storybook/angular:start-storybook executor returns:

return { success: true, info: { port } };

So we want to keep a consistent schema to our @nrwl/storybook:storybook executor.

Now, since we are in control of what the @nrwl/storybook:storybook executor returns and what the options passed to it are, we can generate/infer the whole baseUrl that it ends up with. So, we are passing that to cypress.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated
nx-dev	⬜️ Ignored (Inspect)		Jan 12, 2023 at 2:50PM (UTC)

[nx-cloud]

☁️ Nx Cloud Report

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

📂 See all runs for this branch

---

✅ Successfully ran 5 targets

• nx affected --target=e2e --base=9f19e93d07c6face4f2f9f0e7265b334e3e831c0 --head=75d2c6ebe381b13675d89b1c101e48812e8c5a18 --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox --parallel=1
• nx affected -t test lint --base=9f19e93d07c6face4f2f9f0e7265b334e3e831c0 --head=75d2c6ebe381b13675d89b1c101e48812e8c5a18 --parallel=1
• nx affected --target=build --base=9f19e93d07c6face4f2f9f0e7265b334e3e831c0 --head=75d2c6ebe381b13675d89b1c101e48812e8c5a18 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files root-lint depcheck documentation --parallel=3 --no-dte
• nx-cloud record -- nx format:check --base=9f19e93d07c6face4f2f9f0e7265b334e3e831c0 --head=75d2c6ebe381b13675d89b1c101e48812e8c5a18

---

Sent with 💌 from NxCloud.

[raybotha]

This broke Storybook 6.x
#14373

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.