Allow source components to control how hydrated values are mapped into the clientside model

I'm sure this looks nitpicky … but I'm just trying to use consistent terms to make it easier to spot connections.

📌 Add support for global regions Active is in!

This essentially needs to be replaced with calls to ComponentSourceInterface:::hydrateComponent() … except that the wrapping self::EXPLICIT_INPUT_NAME key should be omitted.

I believe tackling this before 📌 Maintain a per-component set of prop expressions/sources Active would allow that MR to remove the confusing bits in ComponentTreeHydrated.

Yep this makes sense, nice cleanup and decoupling, and I see why it's needed for the other issue.

Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.