Improve i18n support for domain and view forms

[AresEkb]

• I have checked that this feature has not yet been suggested by someone else.

The pull request: #3465

Expected behavior

We need to localize domain and view forms. But there are two problems:

1. Some strings are hard-coded on backend
2. Identifiers of child creation descriptions are locale-dependent. When I add localization files tests become broken

I suggest to fix it and simplify localization

Cuttings backs

No.

Potential side effects

No.

Describe alternatives you've considered

Add a localization on the application level, but it's a way more complicated and impossible for some strings, because they are hard-coded.

What's changed

1. Added EEnumLiteralLabelProvider that gets a localized label for EEnumLiteral

2. Added i18n support for DomainPropertiesConfigurer, MultipleDomainPropertiesConfigurer, FixedColorPropertiesConfigurer, PropertiesWidgetCreationService, NodeStylePropertiesConfigurer, EdgeStylePropertiesConfigurer and some other classes

3. Changed DefaultEditService::getChildCreationDescriptions() and DefaultEditService::createChild(). They used helper.getCreateChildText() to get a localized child description identifiers. So these identifiers changed after I added localization and tests was broken. Now I replaced identifiers by ones of the form: containmentFeatureName-ChildClassName. They guaranteed to be locale-independent and unique

4. Added to DefaultLabelService::getLabel() usage of IItemLabelProvider

5. Removed packages/view/backend/sirius-components-view-emf/src/main/resources/messages/sirius-web-emf.properties. It overrided packages/emf/backend/sirius-components-emf/src/main/resources/messages/sirius-web-emf.properties during tests in GitHub and leaded to strange test fails

6. Added ru localization for several packages