[Bug]: new-frameworks automigration triggered for no reason

[valentinpalkovic]

Describe the bug

When upgrading a project which uses @storybook/experimental-nextjs-vite via npx storybook@next upgrade, the new-framework automigration gets triggered, although the configuration already uses the latest framework configuration.

// ./storybook/main.ts
import type { StorybookConfig } from "@storybook/experimental-nextjs-vite";

const config: StorybookConfig = {
  stories: ["../src/**/*.mdx", "../src/**/*.stories.@(js|jsx|mjs|ts|tsx)"],
  addons: [
    "@storybook/addon-onboarding",
    "@storybook/addon-links",
    "@storybook/addon-essentials",
    "@chromatic-com/storybook",
    "@storybook/addon-interactions",
  ],
  framework: {
    name: "@storybook/experimental-nextjs-vite",
    options: {},
  },
  features: {
    experimentalRSC: true,
  },
  staticDirs: ["../public"],
};

export default config;

Reproduction link

Reproduction steps

No response

System

Additional context

No response