Attach the debugger in the extension content script

[thetarnav]

After meging #25 users don't have to wrap their application with <Debugger> components, for it to be tracked.
Because of this, it should be theoretically possible to inject the debugger script (that attaches the debugger into the reactive graph) with the extension's content script.

Runtime npm library will still be available, and useful for some cases—for example configuring or adding babel plugins.

[thetarnav]

Ok, so there is a different problem that I didn't think of—loading the debugger by injecting a script tag effectively loads a second solid runtime on the page.

This may be a problem, or maybe it won't—it depends if the debugger at any point will need to interact with the application's solid runtime. For example:

• when users want to register their own plugin. Or interact in any way with it.
• when the debugger would need to use some of solid's primitives to get information out of the application graph.

It would be great to be able to just install the extension and that's it, but I think we're stuck with an npm library approach. It's not that bad though.
In the future, we might go in a different direction, that provided a similar experience—there are couple of core solid members that would be happy to add the debugger to solid-start or even solid itself.

[thetarnav]

I'm closing this for now, as this isn't the direction I'll be going currently.