[PP-2] Consider moving ComponentPropsValues::getPropSourceTypePrefixList into source plugins

📌 Move SDC specific validation in ValidComponentTreeConstraintValidator::validate into the SDC source plugin Active is in.

A risk with removing this from the XB-wide storage of explicit inputs (currently ComponentPropsValues in the XB field property named 'props', but 📌 Remove references to 'props' outside of SDC - use 'inputs' instead Active will change that), is that we may lose the ability to apply update paths across all stored XB component trees.

It is the ability to consistently detect what field type the stored input for an SDC prop uses that enables us to e.g. automatically upgrade all SDCs that use an image field+widget to instead use an entity_reference restricted to Media + the Media Library Widget. (See media_library_storage_prop_shape_alter() — which now runs always, but we do not want to prevent the ability for different site owners to make different choices for field type + widget. Nor the ability to change their decision later, which requires the ability to write such an update path.)

Idea:

• Add interface ComponentSourceWithCustomizableExplicitInputStorageInterface extends ComponentSourceInterface, similar to how we already have interface ComponentSourceWithSlotsInterface extends ComponentSourceInterface. Only the SDC component source (and the upcoming "code component" component source) would implement this.
• Add ComponentSourceWithCustomizableExplicitInputStorageInterface:: getPropSourceTypePrefixList().