⚓ T330193 MUL - Make Special:SetLabelDescriptionAliases ready for `mul` language code

@Sarai-WMDE @Manuel Can you please change the copy? The current copy does not seem correct. We are not letting people enter several descriptions in several languages as this currently implies. This special page is also not about creating new Items but about editing existing ones.

Setting to stalled until the copy is updated.

There are at least two other special pages that allow defining descriptions and thus would need to be adjusted to accommodate mul: 1. Special:SetEntitySchemaLabelDescriptionAliases and 2.Special:SetDescription.

1. The first page would follow the same flow shared in this task's description, but probably requires its own ticket.
2. The second page is slightly different: users can input the language code and right away provide a description in the field below. This means that we'd have to disable the Description field based on the immediate user input (e.g. when the input loses focus). I'm not sure this can be done in not a hacky way, or even is a great solution (using a combobox to select the language in all these pages – like we do in Special:NewItem – might be a better idea. This way we could disable on select). At the same time, Special:SetDescription also presents a second, redundant step: users need to confirm their submission of a description after having provided it in the first form. This seems to be an exception (the individual changes to Aliases and Labels made in their dedicated pages are published from the first step). We might want to look into this also in a separate task?

Thank you for checking, @Sarai-WMDE!

1. Special:SetEntitySchemaLabelDescriptionAliases

Based on conversations my assumption was that mul will not be supported for EntitySchemas. But this is ultimately @Arian_Bozorg's call.

2. Special:SetDescription

I considered modifying that page, but decided against it (see also the "not done" section of the epic): The reason was that I assumed this case is not so relevant, and, as you described, the way the page works makes it difficult to intervene before an error message is raised. All in all it seems to be working well enough as is for now.

I hope this helps!

Claiming this also, as the javascript for Special:NewItem and Special:SetLabelDescriptionAliases seems to be shared.

This is entirely untrue, the front end code for Special:NewItem and Special:NewProperty are shared. Nevertheless, I'll keep this task.