feat: allow dynamic routing based on file paths

[Angelmmiguel]

Introduce dynamic routes with parameters in files. For example, [id].wasm or users/[id]/show. The server identifies this pattern in files and configure actix to reply to parametrized URLs.

Note that the same wasm_handler serves all the requests. This means that wws calculates the best worker to reply on every request. The reasons I coded it in that way are:

• We fully control collisions when two workers can reply to the same request (see the Allow dynamic parameters in URLs #10 for more information). Actix will reply with the first handler that matches. However, users cannot set the handlers manually, so we want to ensure a consistent behavior.
• To map an actix path with a runner, we need to create factory service. Note that Actix will create an instance per thread (worker), so Runner instances cannot be shared. This will require multiple instances of the same Wasm module, so the resource consumption will be increased.

I updated the Rust and JavaScript kits and introduced some new examples so you can see how parameter in URLs works.

It closes #10

Pending

• Improve the UI of the JS examples
• Add a new Rust example
• Update the documentation

[ereslibre]

Super cool feature and work! I have some comments regarding compatibility mainly with Windows, and other minor comments.

All in all, I think despite surprising to have brackets at the filesystem level, it is a useful feature when developing locally and prioritizing fast results.

[ereslibre]

🚢 it!

[gzurl]

Is iter() really needed? I think the preferred style is using a reference instead of explicit .iter():
https://rust-lang.github.io/rust-clippy/master/index.html#explicit_iter_loop.

Suggested change

	for (key, val) in handler_result.headers.iter() {
	for (key, val) in &handler_result.headers {