Re-add Windows build

[DominicDirkx]

The Windows build was removed towards the end of this pull request:

tudat-team/tudatpy-feedstock#16

See below a Slack post summarizing the issue with the build:

I had a look at merging this functionality (PR 16, linked above). A few notes:

• Without the move to the new use of the conda-forge cspice, which requires a bunch of downstream changes, which I'm not going to implement just before going on holiday 🙂 , see Use conda-forge cspice #9
• Without the update to tudatpy to support Python 3.12 (fix(python3.12): Update Python setup script to use sysconfig tudatpy#156)
• This pull request on tudat-feedstock was merged succesfully Fix/windows (without cspice update) #8, which was used to build tudat conda package 2.13.0.dev13: https://anaconda.org/tudat-team/tudat/files

Now the problem: using this latest tudat conda package (that was built with the updated version of the tudat-feedstock), leads to a failure of the tudatpy-feedstock

https://dev.azure.com/tudat-team/feedstock-builds/_build/results?buildId=1552&view=results
The OSX/Linux issues I know how to handle (Python 3.12 failure is because of the above issue). But, there is a linking issue for the kernel:
lld-link: error: /failifmismatch: mismatch detected for 'RuntimeLibrary':

>>> CMakeFiles/kernel.dir/kernel/expose_numerical_simulation/expose_estimation_setup/expose_estimated_parameter_setup.cpp.obj has value MT_StaticRelease

>>> tudat_propagation_setup.lib(propagationSettings.cpp.obj) has value MD_DynamicRelease

clang++: error: linker command failed with exit code 1 (use -v to see invocation)

NMAKE : fatal error U1077: 'D:\bld\tudatpy_1722884568021\_build_env\Library\bin\clang++.exe' : return code '0x1'

Stop.

NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.29.30133\bin\HostX64\x64\nmake.exe"' : return code '0x2'

Stop.

NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\VC\Tools\MSVC\14.29.30133\bin\HostX64\x64\nmake.exe"' : return code '0x2'

Stop.

why this is happening now, and not before, I don't know. But, I presume it has something to do with different compiler settings in the latest tudat build.