Update flake.lock, fix errors, get rid of flake-utils

[yannham]

Issue: #67

Description

This PR started as a simple flake.lock update in order to solve #67. However, it got quickly out of hands. I'm not sure exactly how that's possible, but it seems a lot of flake outputs were actually invalid - I suspect newer versions of Nix now check the flake schema more thoroughly, and I got a ton of error about ill-formed outputs. Typically, non-system dependent outputs such as NixOS configurations and overlays were put in flake-utils' forEachSupportedSystem, which they shouldn't.

While trying to get the minimal diff to make it work again, I found that flake-utils was more of a burden than a help, typically because we have several outputs that don't fit the output.<system>.xxx convention. So, this PR gets rid of flake-utils following the technique described in you don't need flake-utils. This required to refactor part of the flakes, because now non-system dependent outputs need to access computed values.

Checklist

Checklist before merging:

• CHANGELOG.md updated
• README.md up-to-date

[ErinvanderVeen]

Any particular reason we care about tree-sitter?

[yannham]

Ah, you caught me red-handed copying stuff someone did to get rid of flake-utils from Topiary 🙃 but no, nothing to do with that (and hi 👋 hope you're doing well !)

[yannham]

I'm not sure what to do about the CI error on cargo dist: this recommends to run cargo dist init, but I can find anything installing the cargo dist command (the cargo-dist crates doesn't). Maybe it's outdated? It can also be solved manually, requiring to download the version of the action, but it's a bit dubious: how did we update in the first place, without breaking the CI?

I'm hesitating between doing what the CI wants, or just ignore this altogether.

[YorikSar]

how did we update in the first place, without breaking the CI?

These versions were updated by order PR #66, and CI was indeed failing there. Per cargo-dist docs, it expects that YAML to match exactly what is generated by the tool:

The happy-path of dist has us completely managing release.yml, and since 0.3.0 we will actually consider it an error for there to be any edits or out of date information in release.yml.

I'd recommend updating cargo-dist to the latest version that uses v4 version (since 0.9.0) of these actions and applying whatever changes to release.yaml it requires. Unfortunately Dependabot doesn't support skipping just one file, so you'll have to keep an eye on its PRs and stop changes to this file manually.

[yannham]

Ok, there was a whole lot of confusion - not least because the cargo dist command is now dist alone, so the recommendation from the error message were outdated and that wasn't really clear to me. Anyway, I've updated dist to the latest version. Happy to get a review on the flake re-org part, @YorikSar !