Dependencies: Update nx dependencies to v17

[valentinpalkovic]

Closes N/A

What I did

Update nx to v17 to accommodate the vulnerability in semver: https://security.snyk.io/vuln/SNYK-JS-SEMVER-3247795

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for 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:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

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

Is this OK to leave here?

[valentinpalkovic]

I don't know who has set up this initially. The value was just moved from the top config to the bottom here. NX says in their documentation that you should use a read-only token here and you could use a write token in your environment variables. https://nx.dev/nx-cloud/account/access-tokens#setting-a-different-access-token-in-ci. But if this one is read-only, everyone would have to set up a nx-cloud.env locally https://nx.dev/nx-cloud/account/access-tokens#using to be able to write to the cache