Fix windows tests

[ocefpaf]

This should fix the detection of nczarr on Windows but will work only on CIs with bash and conda. I guess that is our default environment for developing on Windows anyway. I'm looking into upstream a non-bash script to libnetcdf so we can drop these workarounds.

Closes #1102

[codecov]

Codecov Report

Attention: Patch coverage is 73.33333% with 4 lines in your changes missing coverage. Please review.

Project coverage is 81.79%. Comparing base (f28f321) to head (3213f6d).
Report is 17 commits behind head on develop.

Files with missing lines	Patch %	Lines
compliance_checker/protocols/zarr.py	66.66%	1 Missing and 2 partials ⚠️
compliance_checker/cf/cf_1_9.py	75.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #1104   +/-   ##
========================================
  Coverage    81.79%   81.79%           
========================================
  Files           25       25           
  Lines         5212     5223   +11     
  Branches      1255     1256    +1     
========================================
+ Hits          4263     4272    +9     
- Misses         642      644    +2     
  Partials       307      307           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ocefpaf]

@benjwadams the nc-config bash script is working now on Windows. The error now is probably upstream with nczarr's implementation on Windows:

Error:NCpathcvt: stat=-36 (NetCDF: Invalid argument)
Windows fatal exception: access violation

Current thread 0x000017e0 (most recent call first):

Edit:
I'm going to skip that test until we figure this out.

I was able to get this to work on my Windows machine. Not sure what are the differences here. Investigating... It is quite frustrating!

[ocefpaf]

@benjwadams this one is ready for review. While nc-config is working on Windows now, nczarr is not. I'm debugging this and will open an issue upstream when ready. I'm pretty sure it is unrelated to compliance-checker.

[ocefpaf]

This one had me chasing red herrings all over the code base. I'm not sure if nczarr has a bug, or Python as_uri, or something else. All I know is that we can't have 3 / on Windows, only 2!

[ocefpaf]

@benjwadams while this works, I'm not sure we need this. We can find the version with netCDF4 and let the zarr availability be checked by the failing test. What do you think?

[ocefpaf]

@benjwadams I'd like to go back to #1094 but it would be nice to get this one in first to avoid big conflicts. Do you think you'll have some time to check this one? It is mostly adding Windows tests and a small fix.