Vltava - Data Binding using MatchMaker

[skylerjokiel]

This PR uses the MatchMaker container service to bind two new components: Number and Button.
Spaces also supports these component types, hard coded, so they work in there too.

Number

A component that shows a number. It can also registers with components that produce click events

Button

A components that doesn't contain any state but produces click events that other components listen for.
I actually attempted to make a ButtonFactory that was a container service that provided buttons since they are just ui elements that register. I think this is the right pattern but it would have required a lot of re-working how the component loading flow worked in tabs and I didn't want to commit to doing that so I simply made it a component with no backing data.

Notes

Since MatchMaker is at the Container level all buttons increment all numbers. This isn't great for this scenario but could be useful for other things. I have a plan for how to further scope discoverability and binding within a context.

Also MatchMaker requires components to be loaded before they are registered. This means that when you refresh the button will only increment components that have been viewed on the same page. This is the current behavior of Registro and was known when I wrote MatchMaker. This is okay behavior for a Component surface like Spaces that loads all components but with tabs it requires each tab to be opened. I have thoughts about a MatchMaker that stores handles to components that register with it. It will hydrate components if they are not initialized and someone is producing an event they care about.

[skylerjokiel]

closing this and will re-open with a different scenario since this doesn't really cover data-binding but more action binding which is something we don't necessarily want to promote as a pattern.