Implement HTTP dev server for wrapper hosting

[namesty]

When developing a web application and using a wrapper that's locally available, or under development, one cannot use filesystem URIs as browsers have no access to the filesystem API. So in order to locally access a wrapper from an application, one needs to resort to spinning up the test environment and pinning the wrapper to a local IPFS node or doing things like wrapping the wrapper in a node module, etc. This was highlighted by ChainSafe as one of the cumbersome things of Polywrap fullstack development.

This could be solved by adding a node server to our "default" infra modules. This node server would expose an endpoint to upload wrappers and would serve them. We could make it have a simple "explorer" UI as well.

We could even host a remote instance of it and make it our standard centralized HTTP hosting solution without IPFS, like a http.wrappers.io

This would also entail we'd need to finish #645, which I started but did not finish as it wasn't high priority