Compile time optimizations

[aumetra]

Based on the report @zeerooth submitted, I got rid of the newer ring dependency (which, for some reason, has a build script that runs for a long time) and got rid of the zstd dependency, which also takes a long time to compile native dependencies.

[zeerooth]

Looks pretty good, a minute shaved off!

isolang is still the biggest offender (well, and diesel and async-graphql to a degree)

cargo-timing-20231019T125507Z.html.txt

[aumetra]

I just rechecked on my laptop and apparently the newest ring has a build script that only takes 9s on my laptop.
Therefore I'm opting for keeping ring at the newest version, like before.

[aumetra]

(requesting one last run on your hardware, if you got the time @zeerooth)

[zeerooth]

@aumetra 3m 54s now

cargo-timing-20231023T083229Z.html.txt

[aumetra]

@zeerooth okay, thanks for the run! I'd say that's in the acceptable range of variance.

Looking at the output, ring doesn't break the build times anymore and the additional time can be attributed to the new opentelemetry dependencies and to general compile time variance

[zeerooth]

Indeed, ring is not problematic anymore; out of the dependencies only isolang is the one that really takes a long time to compile, but we discussed that and there's really nothing to improve there because of these repeated long language enums