Prepare for multiple component types: prefix Component config entity IDs with `sdc`

Overview

Blocker: #3469609: Prepare for multiple component types: ComponentTreeStructure should contain Component config entity IDs, not SDC IDs.

1. It should be trivial to identify a component type based only on the component ID (i.e. the Component config entity ID).
2. It should be possible to have component type-specific settings.

Proposed resolution

1. This issue should make this documentation change a reality:
   

   diff --git a/docs/data-model.md b/docs/data-model.md
   index 77eca2bd..72f94183 100644
   --- a/docs/data-model.md
   +++ b/docs/data-model.md
   @@ -243,22 +243,22 @@ Example:
    ```json
    {
      "ROOT_UUID": [
   -    {"uuid": "uuid-root-1", "component": "provider+two-col"},
   -    {"uuid": "uuid-root-2", "component": "provider+marquee"},
   -    {"uuid": "uuid-root-3", "component": "provider+marquee"}
   +    {"uuid": "uuid-root-1", "component": "sdc+provider+two-col"},
   +    {"uuid": "uuid-root-2", "component": "sdc+provider+marquee"},
   +    {"uuid": "uuid-root-3", "component": "sdc+provider+marquee"}
      ],
      "uuid-root-1": {
        "firstColumn": [
   -      {"uuid": "uuid4-author1", "component": "provider+person-card"},
   -      {"uuid": "uuid2-submitted", "component": "provider+elegant-date"}
   +      {"uuid": "uuid4-author1", "component": "sdc+provider+person-card"},
   +      {"uuid": "uuid2-submitted", "component": "sdc+provider+elegant-date"}
        ],
        "secondColumn": [
   -      {"uuid": "uuid5-author2", "component": "provider+person-card"}
   +      {"uuid": "uuid5-author2", "component": "sdc+provider+person-card"}
        ]
      },
      "uuid-root-2": {
        "content": [
   -      {"uuid": "uuid4-author3", "component": "provider+person-card"}
   +      {"uuid": "uuid4-author3", "component": "sdc+provider+person-card"}
        ]
      }
    }
   

2. … and to do that, it will have to update config/schema/experience_builder.schema.yml.
3. It also means that the client-to-server data model transformation at ::clientLayoutToServerTree() needs to have its logic updated. @longwave opted to instead update the client where necessary, which was … virtually nowhere! 🚀 That means #3475584: Add support for Blocks as Components will be slightly easier!

User interface changes

Zero changes.