Add versions.edition column to the database and expose it on the API

[Turbo87]

This addresses part of #1541 by reading the edition field of uploaded Cargo.toml files, saving the value in the database and then exposing it on the API.

Note that this does not include any backfilling for previously uploaded crates. Should we move the API part to a dedicated PR and merge it only after we have backfilled the data?

Related:

• Display "edition" from manifest on crate-page #1541
• Edition: Implement as_str() fn LukeMathWalker/cargo-manifest#58

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.19%. Comparing base (88f856d) to head (934d3fb).
Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9932      +/-   ##
==========================================
+ Coverage   89.18%   89.19%   +0.01%     
==========================================
  Files         294      295       +1     
  Lines       30713    30753      +40     
==========================================
+ Hits        27390    27429      +39     
- Misses       3323     3324       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[LawnGnome]

👍

Note that this does not include any backfilling for previously uploaded crates. Should we move the API part to a dedicated PR and merge it only after we have backfilled the data?

Your call, but I feel like we can merge this as-is and just not tell anyone until the backfill has occurred. 🙂

[Turbo87]

until the backfill has occurred

the backfill has occurred 😉

the script to generate the backfill data is available at https://github.com/Turbo87/crates.io/blob/backfill/edition/src/bin/backfill-edition.rs