[PP-1] Make config translation settings form order the same as the formatter and widget settings

Problem/Motivation

Follow-up for #2546212: Entity view/form mode formatter/widget settings have no translation UI, from the usability review in #2546212-246: Entity view/form mode formatter/widget settings have no translation UI. The translation form of an entity display shows the settings in the order of the config schema. The formatter or widget settings form can use a different order. Example: the Boolean formatter shows "Custom output for TRUE" before "Custom output for FALSE" on "Manage display". The translation form shows FALSE before TRUE. Translators can mix up the two values.

Steps to reproduce

1. Add a Boolean field. On "Manage display", select the custom output format and enter text for TRUE and FALSE.
2. Open the translation form of the view display.
3. The FALSE value is shown before the TRUE value.

Proposed resolution

To be discussed. Options:
- Change the order in the config schema and in defaultSettings() of the Boolean formatter. This fixes only this formatter.
- Use the element order of the settings form in the translation form. This fixes all formatters and widgets, but is more complex.

Remaining tasks

-

User interface changes

-

Introduced terminology

-

API changes

-

Data model changes

-

Release notes snippet

-