CLI: Improve error handling when dealing with angular.json files

[yannbf]

Closes #22350

What I did

The Storybook CLI now throws different errors and requests the user to file an issue to provide us more information. Regarding #22350 so far we found no way to reproduce the issue, so we rely on the community to bring that up to us.

How to test

1. Get an angular sandbox with no Storybook
2. Delete all projects on the angular.json file, or make the key contain an empty object, the following error should be thrown:

Error: Storybook was not able to find any projects in your angular.json file. Are you sure this is an Angular CLI project?

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

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

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