Vite: Update dep range for @storybook/mdx1-csf

[IanVS]

What I did

A change was made in @storybook/mdx1-csf which we are relying on here, so we need a more precise version range in our dev and peer deps. Otherwise things will break for users who have an older version of mdx1-csf installed and try to use it by setting the feature flag.

How to test

Install @storybook/mdx1-csf@1.0.0-next.0 and enable mdx1 feature flag in a vite project, and you'll get something like mdx is not defined. Install @storybook/mdx1-csf@1.0.0-next.1 and it will be fixed.

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

[ndelangen]

@shilman 👀 ?