fix: normalize API routes using Rust path entities

[Angelmmiguel]

In the current main version, file paths are not normalized properlies as APIs. This is causing inconsistent behaviors in different environments:

• In unix, the API path includes the root folder the CLI receives as argument. For example, for wws ./examples/js-basic, the URL of the handler.js should be /handler. Note that ./examples/js-basic is the local folder to read the files, not a prefix for the final URL. However, the HTTP endpoint it generates is `/examples/js-basic/handler.
• In windows, it just doesn't work. The handler.js is not accessible (See [1]).

This is mainly caused by converting file paths to string and apply transformations later. Since paths may include special components such as . and ./, applying operations like replace can have different outcomes depending on the environment. This also causes inconsistent behaviors when a final backslash is added or not to the CLI argument.

In this PR, I changed that implementation to run all required transformations directly on the path. Instead of replacing and subtracting from a converted string, I iterate over the components to remove any special entity and keep only the Normal ones. Finally, I convert them to a String to be used as the API path.

I tested the current changes on both Windows and Mac (Unix) and they work great:

[1]

It closes #30

[Angelmmiguel]

I found an error when testing subfolders in Windows. It's using the \ separator and that's causing actix not to define the route properly.

[ereslibre]

Looking great, lots of tests! A couple of comments :)

[ereslibre]

LGTM, thanks @Angelmmiguel! It looks great! Just a small optional comment about the GH workflow setup

[ereslibre]

🎉

[assambar]

Ship it!