Change forceReRender story to forceRemount

[JReinhold]

What I did

We have an internal CI story that tests that components remount when forced to - by asserting that a button looses focus after the event. However it was actually emitting FORCE_RE_RENDER, while actually it is the FORCE_REMOUNT that should trigger that behavior. Which is why I've changed it.

I've also enabled Vue for the tests, as that use case was recently fixed by #20712

How to test

See all sandboxes in Chromatic should actually be correct now.

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

[JReinhold]

@tmeasday this was naive of me. emitting FORCE_REMOUNT will immediately replay the play function, making it loop forever both in Storybook and Chromatic. What should we do here?

1. Remove the test completely - it wouldn't be a huge loss since it has never worked, but on the other hand it would be nice to know that remounting works in the renderers.
2. pass an option like skipPlay when emitting the event, and pass that all the way through to StoryRender.render(). I'm not sure this will work, or if it will break the whole flow in another way.
3. ... other suggestions.

[tmeasday]

I don't think we should do anything fundamental to make the story work (if that's what you were suggesting in 2.

But can we do something a little hackier? Like only run the play function once per second or something like that?

I'm not sure if the story remounting is going to cause a problem for chromatic anyway perhaps, but at least this way we could test it manually (i.e we might need to disable chromatic).

[JReinhold]

@tmeasday I've been through every single published Storybook now, and they all work as expected: alternating between focus and blur every 3 seconds. The story is disabled in both Chromatic and the test runner.

I think we should just merge this in and solve the Chromatic issue separately when we feel that is a priority.