Migrate Windows CI from vcpkg to conda-forge

[j-rivero]

We are using vcpkg to implement our CI on Windows, particularly to get external dependencies and inject them using -DCMAKE_TOOLCHAIN_FILE into colcon to build all ignitions from source.

Our documentation is recommending to use conda-forge for having binaries installed on Windows and would be good to move our CI infrastructure to follow the tools we recommend for end-user experience. One option could be to replicate the vcpkg setup and install the dependencies and use colcon to build all libraries together from source. A second step could involve to have conda-forge packages for every ignition library and only build from source the library under testing (like we do in Ubuntu with apt).