Angular: Fix initialization of Storybook in Angular 16.1

[valentinpalkovic]

Closes #23568

What I did

Fixed initialization of Storybook in Angular 16.1. An nx project was wrongly recognized, because @angular-eslint/schematics introduced a dependency on nx. I have removed the logic to identify a workspace being a nx workspace by evaluating nx as a dependency. Instead, we only rely on the existent of a nx.json file, since that should be enough to identify a workspace using nx or not in most of the cases.

How to test

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

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.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "build", "documentation", "maintenance", "dependencies", "other"]

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

[yannbf]

Sounds good to me! I guess nx.json will always be present in Nx projects.

cc @mandarini