Add server logs

[localjo]

This pull request adds server logs to the devtools. Once it is merged it will resolve #1

[localjo]

@pushred This commit adds the server logs to the panel via socket.io, so they'll stream in as new messages are logged. Styling will be improved when I attack issue #2 but there may also be some room for improvement in the future with the format of the logs (right now they're just strings). Future log enhancements might call for some additional CSS or syntax highlighting or something.

@joanniclaborde you probably know best what would be feasible/useful to output in the logs in addition to what's there now.

[pushred]

Note that I've rebased https://github.com/solidusjs/solidus/tree/stream-log-to-web-socket to pull in the new Solidus header.

No comments on the code front, this is all super straightforward. Works as advertised!

I've definitely got a lot of ideas on ways to present the logs (special handling around exceptions, slowness, resource fetching) but I think it's all going to require structured data to be provided vs. the simple strings we have now. Switching to a logging library that'll facilitate that is definitely the plan but Joannic will be focusing on another project for much of this month. So this is totally fine for now. Perhaps if anything you can color code the log entries a bit with some simple string matching.

You'll definitely need to prioritize displaying the logs in a scrollable panel that keeps the scroll position at the bottom, like the console, terminal, etc. But as you noted #2 will take care of that.

Another detail would be standardizing any feedback concerning the Solidus server connection, i.e. "Looks like you're not inspecting a Solidus Page", "Socket Disconnected", etc. I'd present those big & centered in the panel. Messaging could be better as well. The first message isn't bad though I'd consider removing the tab altogether if possible in this scenario. The latter something like "Your Solidus dev server doesn't seem to be running anymore" would be good.

We'll also need to figure out how to communicate the Socket.io server to you, I think another header would work for that. If it isn't present you'd disable this functionality as that would signal either an older Solidus server or something running in a production environment which should definitely not be running the server. Perhaps there might also be some value in adding a header with the current environment to communicate that (and explain missing features).