React: Don't show decorators in JSX snippets

[tmeasday]

Telescoping on #21902

An alternate solution for #21649

What I did

Always move the JSX decorator to the end of the list, so it avoids all other decorators, as we can't see "inside" decorators in React. However we still need to actually render all the decorators as the story may depend on them.

TODO:

• Figure out type issue with decorated.
• Add an option to disable this behaviour.

How to test

See stories in this PR:

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]

I think this is an interesting solution.

1. Does it make sense to do something similar for all renderers?
2. Long-term, if we want to unbundle addon-docs as much as possible from the renderers, this would cause trouble right? Then we can't just import the jsxDecorator into the renderer anymore. I wonder if we should instead allow decorators to set some sort of ID on themselves for situations like this. This is very long-term though.

[tmeasday]

@JReinhold as far as we currently understand it, the issue is only a problem for react (well maybe there's an issue in that you see all the decorators in other frameworks but at least you see the story inside them).

So we think as a patch release a localised fix like this is a good idea.

Probably a better solution would be some 1st class way to declare a decorator as an "story inspector" or something so it gets wrapped inside the other decorators. Unless we can find a better solution I'd propose that as a 7.1 PR