Disable default XB components

HAH! I wrote pretty much the same thing over at #3498337-3: When demo_mode, limit component list to only SDCs provided by the active theme (and not subthemes) → . I think this is relevant now, because XB is included in Drupal CMS now.

In fact, I think the scope described in the issue summary is too narrow. I think we should change:

Experience Builder ships with a bunch of components for development purposes. We don't want these enabled in the Drupal CMS demo, and should curate the ones that are enabled.

to:

Experience Builder ships with a bunch of components for development purposes, and exposes all SDCs of the active theme, including SDCs of the base theme. Drupal CMS ships with a subtheme of Olivero: drupal_cms_olivero. We don't want ANY SDCs enabled in the Drupal CMS demo of XB, only those provided by drupal_cms_olivero.

Proposed solution

AFAICT Recipes' wildcard support combined with the disable and enabled config actions should be sufficient? Essentially:

# First, disable all Component config entities XB generated during installation.
experience_builder.component.*:
  disable: []
# Then, enable only the Component config entities provided by Drupal CMS.
experience_builder.component.sdc.drupal_cms_olivero:
  enable: []

Thoughts? 🤓

Per #4.

Gave this a quick manual test and it pretty much works as intended. The variable-length config names threw the recipe system for a loop, so that might be a problem much later down the road, but this is fine for now.

Screenshot of the sad components list:

(The fix: let's commit more components!)

Merged into 1.x and cherry-picked to 1.0.x. Thanks for the neat idea Wim!

🤩