[Documentation]: Improve visibility of argTypesEnhancers and argsEnhancers

[mrginglymus]

Describe the problem

I've recently discovered these two parts of the preview API in my efforts to speed up and simplify my automatic storybook controls. I actually raised a discussion (#30082) where I suggested adding an API matching their behaviour before I had found them!

They are very powerful yet simple tools that allow users and plugin developers to provide control information without excessive boilerplate, and so I think storybook would benefit from having them documented more visibly.

I had considered a PR to add some documentation, but I couldn't even begin to work out where it would go (:

Additional context

No response

[shilman]

It is an intentionally undocumented API. Today we use experimentalX as a naming convention for stuff like this, but we didn't back when we added those APIs. I think if we were doing it today we would've called it experimentalArgTypesEnhancers and it probably would stay experimental for a long time.

[mrginglymus]

edit: obligatory xkcd#1172

There are some orphaned documentation files referencing it still:

• storybook/code/addons/docs/docs/multiframework.md

  Line 46 in 82b2951

  export const argTypesEnhancers = [enhanceArgTypes];

• storybook/code/core/src/preview-api/README-store.md

  Line 96 in 82b2951

  To add a argTypes enhancer, `export const argTypesEnhancers = []` from `preview.js` or and addon

which may want tidying up then (unless those are internal docs...)

---

I suppose my question then becomes either

1. Is there anything that can be done to stablise the API

or -

2. Is there a plan for an equivalent (or better) new API e.g. in CSF factories

Either of which I'd be keen to contribute towards, as these existing apis have so far proven extremely useful.