Improve schema for "allowed_html" to provide a better config diff

This is still very relevant today. We should match ckeditor, for example from core/profiles/standard/config/install/editor.editor.basic_html.yml:

settings:
  plugins:
    ckeditor5_sourceEditing:
      allowed_tags:
        - '<cite>'
        - '<dl>'
        - '<dt>'
        - '<dd>'
        - '<a hreflang>'
        - '<blockquote cite>'
        - '<h2 id>'
        - '<h3 id>'
        - '<h4 id>'
        - '<h5 id>'
        - '<h6 id>'

I agree that this issue remains pertinent, especially considering the structure used by CKEditor in Drupal core.

Adopting a similar format for the "allowed_html" setting, as demonstrated in core/profiles/standard/config/install/editor.editor.basic_html.yml, would not only ensure consistency with CKEditor's configuration but also improve clarity and manageability for developers and site administrators.

Such alignment could greatly enhance user experience and reduce configuration errors.

This at minimum soft-blocks 📌 [PP-2] Make FilterFormat config entities fully validatable Postponed and potentially hard-blocks it.

Glad I found this issue, this is a problem every single time we change filter formats in any way, especially when (for example) adding new styles.

What do people think of an interim solution where we keep the existing unstructured string and at the very least sort the tags alphabetically? That would at least alleviate very hard to parse diffs like the following:

This is an example where a new style had been added to the table element, but all the other tags were randomly reordered.

#93++ — let's do that here so we can close this already ~100-comment long issue? 😄