Consider doing an MF6 examples nightly build, or include them in the MF6 nightly build. Currently we have a development version of the RTD site but we only release examples (i.e. build and distribute input files from the Python/FloPy scripts) at "official" MF6 release time.

The ultimate aim here is consistent versioning for MF6 and MF6 example models. Since they must be synchronized to the same set of DFNs, IMO they should be on an identical release cycle. (Moving them into the same repository is one way, but might be tricky and they have lived separate for a long time, so I am ignoring that possibility for now.)

Immediate motivation is that we already have tooling which can identify/install both official and nightly MF6 binaries (latter identified by date), but we have had no easy way of installing examples, and in any case we currently only distribute "official" examples releases. The example models API under development is a tentative solution, but ideally it should have the same version semantics as flopy's get-modflow for the mf6 official or nightly build.

Maybe one way to do this, for reduced maintenance burden, is to consolidate the "full" and "minimal" build flavors and make the nightly build contents identical to the official. This will mean mf6 release automation needs to build the examples/docs itself, instead of downloading the release from the examples repo