Core: Remove state deprecation warnings by default

[tmeasday]

Closes #20728

What I did

Move deprecation warnings for old state fields so they don't always trigger.

I wanted to have these deprecations be defined in the file that defines the relevant APIs, but it was hard to avoid a getter being called when the substate was being cloned into a larger state. There's probably a tricky way to do it, but I think this is fine. We are only concerned with people calling useStorybookState anyway.

How to test

1. Check for lack of warnings in a sandbox by default
2. Call useStorybookState().storiesHash in the manager somewhere, say in .storybook/manager.jsx:

import React from 'react';
import { useStorybookState, addons, types } from '@storybook/manager-api';

addons.register('xyz', () => {
  addons.add('xyz', {
    type: types.TOOL,
    title: 'test',
    render: () => {
      useStorybookState().storiesHash;
      return <div />;
    }
  });
});

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