Improve the plugin editor UX

[Calinou]

• Make the subfolder path and script path optional.
  • If empty, the default subfolder path will be the plugin name converted to snake_case.
  • If empty, the script path will be plugin.<ext> where <ext> is the extension of the script language chosen.
• Add tooltips to all fields.
• Align labels to the right to be closer to the text fields.
• Rename the "Update" button to "Refresh" in the plugin list as it doesn't actually update plugins, just refresh the list.

Creating plugins has never been faster. Now, you just need to fill in the Plugin Name field and you're good to go 🙂

See #36636.

Preview

[YeldhamDev]

Align labels to the right to be closer to the text fields.

We should try discussing about making this consistent across the editor, as most labels of this kind align to the left.

[aaronfranke]

If empty, the plugin path will be plugin. where is the extension of the script language chosen.

You mean the script name?

[Calinou]

@aaronfranke Yes, I meant the script path. I corrected OP 🙂

[Calinou]

By the way, is there an use case for creating a plugin without enabling it immediately once it's created? If not, we could always enable new plugins and remove the "Activate now?" checkbox to further simplify the plugin creation dialog.

[aaronfranke]

Yeah, that checkbox should be removed. An empty plugin has no behavior, so it doesn't matter if it's enabled or not on creation.

The default state should be enabled so that it works if class_name scripts are added, though many things would still need the plugin to be manually restarted.

[KoBeWi]

It would be nice to have it rebased after #41788
Making the fields optional is really useful.

[akien-mga]

Superseded by #60865 (partially, some bits might still be relevant for a new PR).