Update from_copernicusmarine ingestion

[VeckoTheGecko]

• Update from_copernicusmarine to parse in W fields from CF naming - fixes Update .from_copernicusmarine to parse vertical velocities #2237

• Update from_copernicusmarine allow no currents (no log messages are emitted here) - fixes FieldSet.from_copernicusmarine() and non-advection kernels #2236

Note that if there is a W the UV field isn't added - is this in line with v3 @erikvansebille ?

[erikvansebille]

Note that if there is a W the UV field isn't added - is this in line with v3 @erikvansebille ?

Yes, that's correct. We by default have either a UV or a UVW VectorField

[erikvansebille]

Should we also add #2235 (comment) into this PR?

[VeckoTheGecko]

Should we also add #2235 (comment) into this PR?

I want to do that now separately alongside a bunch of other runtime warnings we're getting Actually, I can do it here - wont take long

[VeckoTheGecko]

I want to do that now separately alongside a bunch of other runtime warnings we're getting Actually, I can do it here - wont take long

I think we only see these in the tests actually - let's merge this

[erikvansebille]

I checked that most (all?) copernicusmarine products use "upward sea water velocity" as default name for "W".

However, that this means that, since depth is decreasing downward, we will have to negate the W field by default...

Note that this is also done in v3:
https://github.com/OceanParcels/Parcels/blob/4073545a8ac4a0a49469277eb7603dd6a4c6cb0a/parcels/fieldset.py#L656-L657