Storybook: Cleanup potentially unnecessary action spies

[tyxla]

In order to get the Storybook v8 upgrade to pass in #67574, I added some action spies, because without them, I was getting these errors for a few stories:

See these for more details:

• The action spies I added: 7bfce92
• Migration docs: https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#implicit-actions-can-not-be-used-during-rendering-for-example-in-the-play-function
• Discussion: Storybook: Upgrade to v8.0.x #67574 (comment)

We believe that this isn't an optimal solution, as this feels like a false positive.

So, we should remove those action spies, but to do that we need to learn what really tricks Storybook into causing those errors, and how we can work around it better.

cc @ciampo

[t-hamano]

There is a work in progress to replace all implicit actions with explicit ones.

All of argTypesRegex will be removed, but is this issue still worth investigating?

[tyxla]

@t-hamano nice!

Unless I'm missing something, if we get rid of argTypesRegex, we will be able to also revert 7bfce92 and close this issue.

Don't hesitate to ping me for reviews or anything related.

[t-hamano]

I forgot to link the PR: #70589

[im3dabasia]

From what I understand to have actions show up in the Storybook UI, we need to use one of the following approaches:

1. Using argTypesRegex:
   This is a global way to automatically generate actions for props that match a certain pattern—commonly those starting with on, like onClick or onChange. It’s convenient since it requires no manual setup. However, as of Storybook 8, this is no longer the recommended approach.

2. Manually defining actions in the args object:
   This is the recommended method according to the Storybook documentation. It involves explicitly defining the actions using args, as shown in this example.

After this commit, we had three stories—Tabs, TabsPanel, and CustomSelectControlV2—that included both implicit (via argTypesRegex) and explicit action definitions.

With this PR, we aim to remove the use of implicit actions in those stories and rely solely on the manually defined ones—bringing them in line with the goal outlined in this issue.

[tyxla]

This can now be closed after #73502 landed.

Thanks for the work on it @im3dabasia @t-hamano!