Track crate dependency count over time

[emilk]

What

• Part of Minimize crate deps of the logging SDK to improve compile times #4788
• Closes Track compile-times and dependency count of rerun-sdk over time #5101

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct
• I've included a screenshot or gif (if applicable)
• I have tested the web demo (if applicable):
  • Using newly built examples: app.rerun.io
  • Using examples from latest main build: app.rerun.io
  • Using full set of examples from nightly build: app.rerun.io
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
• If applicable, add a new check to the release checklist!

• PR Build Summary
• Docs preview
• Examples preview
• Recent benchmark results
• Wasm size tracking

[jprochazk]

TODO:

• the bash expression to count dependencies is undercounting

[github-actions]

Size changes

Name	main	5228/merge	Change
re_sdk --no-default-features	(none)	117 crates	+100%
re_viewer --all-features	(none)	408 crates	+100%
rerun --all-features	(none)	435 crates	+100%

[emilk]

The undercounting might be because we don't count build-dependencies 🤔

[emilk]

The dependency count is off by quite a lot, but maybe this is still a good start.

cargo check -p re_sdk --no-default-features says 213 deps
scripts/ci/count_dependencies.py -p re_sdk --no-default-features says 118
cargo deps-list -p re_sdk --no-default-features says 165

cargo check -p re_viewer --all-features says 504
scripts/ci/count_dependencies.py -p re_viewer --all-features says 329
cargo deps-list -p re_viewer --all-features says 368

Importantly, adding e.g. meilisearch-sdk = "0.24.3" to a Cargol.toml makes the count jump by 59, which should be a strong warning signal.

[jprochazk]

Can we try to compare against what this outputs? https://docs.rs/crate/cargo-deps-list/latest