sbcl: 2.0.0 -> 2.0.8; add 2.0.9; lispPackages: regenerate

[7c6f434c]

Motivation for this change

#94913 and stuff getting stale

README on updates missing some useful pointers

unblocks #92763 I guess

Will self-merge once checks pass

Things done

Entire lispPackages build, no sbcl_2_0_2 references in Nixpkgs

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

[7c6f434c]

@ofborg build lispPackages lispPackages.query-fs

[purcell]

Nice! Was there a compatibility issue with bumping directly to 2.0.9?

[omasanori]

@purcell Zach Beane Common Lisp – New SBCL 2.0.9 behavior breaks some stuff warns such issue, so @7c6f434c and I did not make 2.0.9 as the default one.

[purcell]

Ah, makes sense! I thought it might be something like that. Great work!

[7c6f434c]

@purcell, it was kind of the same the previous time with 2.0.0 vs 2.0.1 too, SBCL does an apriori very reasonable thing but there are fragile and useful packages that need a bit of time to adjust.