@tenguiz

As a colleague of dke, I have reviewed his suggestion in the context of our use case and made a few small improvements:

1. Removal of the Update Hook: I have removed the update hook, as it was only setting the new configuration to false. This is unnecessary because undefined keys are treated as null, which is equivalent to false in a boolean context.
2. Adjustment of the Query Filter: I adjusted the query filter to ensure that it prevents invalid LDAP queries, regardless of whether the parentheses are present or not.

This code change now successfully deactivates users who no longer meet the filter criteria, thereby resolving the issue we encountered.

tenguiz → made their first commit to this issue’s fork.

When installing entity_browser, inline_entity_form, lightning_media, lightning_media_image I had no problems.
But later on, the config import failed with the mentioned error.

After I applied the schema change from the merge request, the config import works again.

RTBC

I have developed a patch.

Drupal::languageManager()->getCurrentLanguage()->getId() gets the current language code of the website. This can be passed to drupalSettings.googleTranslatorElement and used as pageLanguage for the new TranslateElement.

It would also be possible to leave pageLanguage undefined. Then google tranlsate will automatically set the source language.