Refactor building and testing under Windows

[ssbarnea]

Building and testing our extension under Windows was always problematic due to its special WSL related requirements. New changes introduced by WSL2 uncovered some serious performance problems which will require us to gradually implement the following set of changes:

• Use native Windows build-chain instead of WSL one
• Use a WSL based python virtual environment to install ansible-dev-tools because this is the only way to use the under windows other than the containerized form. Using native Windows python is not supported because ansible-core does not support it and it will never work.
• Check if current python is Windows based at runtime and fail with explanatory message (will help new users a lot)

Reasoning

Filesystem access between WSL2 and Windows is extremely slow (10-50x slower than in WSL1) and this make the building of extension extreme fast, affecting webpack in particular which can take 1h 20min instead of less than 5 minutes.

Github Actions does not allow us to configure a GITHUB_WORKSPACE directly into WSL machine and most official github actions do not provide access outside the workspace. This means that the codebase will reside inside Windows and not WSL during testing.

These two facts that are outside our control, forces us to aim for using Windows for development and WSL only for the ansible-dev-tools installation, which should also be optional as some users might want to just use our extension with containers.