Oops, guess I hadn't finished and brought the namespace into the XAML, pushed a fix. Hope that's it.

If it all works, then I should spend a bit more time bringing in rest of tests and samples.

Should remove the TODO that ignores the thing about docs needing samples.

I did check the build logs and see that in the tooling module it pulls the extension package from our artifacts feed, but here where we're doing the project reference it doesn't. So, I think we're good on that front!

Should mean that we can use this similar setup now for other packages or the sample app if we need to pull in other Toolkit components, we can test things and iterate as needed in the main repo, and then push to packages for the components to consume via the feed in other repos via the tooling module... FYI @Arlodotexe

Was just a bigger pain in particular here with how ingrained the extensions were and needing to tease out the namespaces to be unified and get to a place where we were good building. Hopefully anything else we start needing isn't as critical and we can bring to be unified first and build on top of that instead.

Some issues with threading, CI should pass now and tests run.

Let's review and merge this to get everything stable on top of the extensions, and then I can add another PR later as needed to finish samples/tests.