Add registry-aware controls

[youknowriad]

Related #13662 Requirement for #13088

In some situations, you want to build controls that target another store from the registry. Until now we were relying on the global select or dispatch functions but the issue is that it only targets the default registry. If we have a separate provider, this might not work as expected. In this PR, I'm introducing a createRegistryControl helper used to mark a control a cross-stores control with access to the registry object.

const controls = {
   TYPE_OF_CONTROL: createRegistryControl( registry => (args) => {
      // Do something with registry
   })
}

This PR also includes a follow-up performance improvement to the registry-aware selectors.

[nerrad]

Looks good to me 👍

[aduth]

This all seems sensible to me, but I've got some burrowed worry about how this actually works, when we'd have some separate RegistryProvider. I guess it might rely on some registry clone behavior like considered in #7453, which would re-assign the registry for the selectors / controls in the process of undergoing the clone?

[youknowriad]

@aduth That's a good point, I thought about it and yes it's challenging if we map the selectors and controls inside the store creation funciton. It means the clone function needs to reassign the selectors/controls somehow while if done at the registry level It would be generic, easily clonable but at the same time a little bit less performant.

I think this should be reconsidered as part of the "clone" implementation and whether the performance gain in long posts is important enough to be worth the added complexity.