[vtadmin] Further generalize DangerAction into ActionPanel

[doeg]

Description

Further adventures in generalizing the DangerAction component! The original is very well-written + made these refactors nice and straightforward. :chef-kiss:

• Renames the component from DangerAction to ActionPanel, and adds a danger prop to preserve the scary styling when necessary. 🎃
• Updates all of the mutation triggers on the tablet/advanced page to use ActionPanel in its less scary form.
• Makes the confirmation input optional.
• Adds a disabled prop
• Lots more tests

Using ActionPanel under the hood, everything works as before:

Related Issue(s)

• Continuation of [vtadmin] Further generalize DangerAction component #10319
• Prefactor for [vtadmin] Reload schema in shard #8723, [vtadmin] Reload keyspace schema #8738

Checklist

• "Backport me!" label has been added if this change should be backported
• Tests were added or are not required
• Documentation was added or is not required

Deployment Notes

N/A

[doeg]

I noticed that this copy is currently:

Command StartTablet cannot be run on the primary tablet.

I think it should probably be (emphasis mine)

Command StartReplication cannot be run on the primary tablet.

... But wanted to call this out in case I'm missing something. Same deal with the StopTablet -> StopReplication copy change below.

[github-actions]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has the correct release notes label. release notes none should only be used for PRs that are so trivial that they need not be included.
• If a new flag is being introduced, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive.

Bug fixes

• There should be at least one unit or end-to-end test.
• The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.

Non-trivial changes

• There should be some code comments as to why things are implemented the way they are.

New/Existing features

• Should be documented, either by modifying the existing documentation or creating new documentation.
• New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• vtctl command output order should be stable and awk-able.

[ajm188]

🎵 hiiiiiighhhhwaaaaayyyyy to theeeeee ActionPanel 🎵