move the nightly env into its own file

[keewis]

This avoids having to build binary dependencies on e.g. RTD in order to lock the dependencies.

This won't actually do anything besides accelerating the locking, until we change the upstream-dev ci. For that we need to have parcels-code/pixi-lock support the manifest-path or working-directory options of setup-pixi (cc @VeckoTheGecko), and we also need to change the commands we use to run the tests. I may be able look into both this week.

Ultimately we're working around two restrictions in pixi with this:

• conda dependencies are resolved first and cannot be changed when resolving pypi dependencies
• source dependencies are built into wheels when locking to figure out dependencies, which means this always happens first, regardless of whether the environment is then actually used.

For reference, I saw @TomNicholas did something very similar for virtualizarr a couple of months ago, except that is using pip to modify the environment.

[keewis]

this appears to be ready now. The failing upstream-dev tests are also visible on main (I'll bump the version of the reporting action in a separate PR so we actually get an issue for these).

Edit: not sure what to do about the mypy internal error. I'd probably investigate this in a separate PR.

Note that this depends on Parcels-code/pixi-lock#21, so we should merge only after that was merged and the references to my fork were removed (cc @VeckoTheGecko)

[keewis]

this should be ready for reviews now (the nightly CI fails with the same errors on main, too)

[keewis]

actually, I'll go ahead and merge this now. Any DX improvements (like creating a pixi task to run the nightly tests) can be separate PRs.

As usual, if this breaks anything we can revert and I'll investigate afterwards.