everything is unstable

[cdmistman]

Why

it's annoying having multiple nix channels that affect some modules but not others. also it's a lot easier to keep things up-to-date and consistent when we're only using 1 channel. also 23.05 is almost deprecated, and our choices were to either:

• upgrade to 23.11
• stick with 23.05 as it becomes more and more out-of-date (things aren't always backported to the stable channel!)

What changed

• removed nixos-23.05 channel input
• changed everything to rely on nixpkgs-unstable instead
• update usage of graalvm due to upstream changes in how graalvm is versioned
  • this is ok because afaict we're not using the java nixmodule anywhere anyways! will need to test more extensively once we move java templates over though
• removed the python 3.8 nixmodule from the current modules list due to a version incompatibility with sphinx (which i guess is somewhere in the dep tree)

Test plan

• template tests still pass :)

Rollout

Describe any procedures or requirements needed to roll this out safely (or check the box below)

• This is fully backward and forward compatible

[ryantm]

Why are we getting rid of python 3.8?

[ryantm]

Oh, I see

removed the python 3.8 nixmodule from the current modules list due to a version incompatibility with sphinx (which i guess is somewhere in the dep tree)

What's the error?

[cdmistman]

something like sphinx-x.x.x is not a valid interpreter for python 3.8?

[cdmistman]

it was an error printed by nix (not printed from within a drv) so i think this is just an incompatibility with the latest unstable