Build: Update nx to 22 and invalidate cache when scripts change

[Copilot]

Closes #

What I did

Updated nx tooling to v22 and added cache invalidation for script changes. The upgrade removes deprecated useLegacyCache option and adds runtime script tracking to bust cache when files in scripts/ directory change.

Changes:

• Upgraded nx, @nx/vite, @nx/workspace from 20.8.2 to 22.0.3
• Removed useLegacyCache: false from nx.json (no longer supported in v22)
• Added autoExit: true to tui config for better CI automation
• Added runtime script-change tracking to sharedGlobals:

  "sharedGlobals": [
    "{workspaceRoot}/tsconfig.json",
    {
      "runtime": "cd .. && git ls-files scripts | sort | git hash-object --stdin-paths | git hash-object --stdin"
    }
  ]

• Resolved merge conflicts with latest next branch (regenerated yarn.lock)

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

No manual testing required. Dependency upgrade with configuration changes that will be validated by existing CI workflows.

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-storybook/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 publish.yml --field pr=<PR_NUMBER>

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.