Acquia DAM and Experience builder integration support.

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

vishalkhode → changed the visibility of the branch 3519247-approach-1 to hidden.

Updated MR with necessary changes, requesting review.

chandu7929 → changed the visibility of the branch 3519247-acquia-dam-all-media to hidden.

The approach in this MR is incompatible with what I've heard @lauriii describe: support both core's Image MediaType and Acquia DAM images at the same time.

👉 📌 Decouple image shape matching from the `image` MediaType Active paved most of the path for this to work the way that I've heard @lauriii describe it, but you'll first need to do 📌 Support image shape matching from the `image` MediaSource: support both the `image` + `oembed` MediaSources simultaneously Active to make it entirely possible. I've included clear next steps.

More concerning: the way this MR currently works is by introducing a completely separate prop shape, which means that all existing SDCs/code components won't work! Plus, the sole SDC that uses that new prop shape is adding half a dozen or so props that would present concerns to the content author that they should never see.

Due to the fact that code components are hard coded to image schemas, and that we need to define our own schema to start asset, external, and version IDS.. marking postponed until 📌 Support image shape matching from the `image` MediaSource: support both the `image` + `oembed` MediaSources simultaneously Active lands.