feat: Add edition for scripts anytime we mutate the manifest

[epage]

What does this PR try to resolve?

This is an experiment in finding a middle ground between two opposite perspectives

• cargo fix resolves the no-edition warning by setting it
• cargo automatically injects the edition whenever running a cargo script

This is instead "if we're already doing edits, we might as well inject the edition". This is still limited because (1) people or IDEs can do direct edits and (2) cargo add -M script.rs serde is a big more cumbersome than cargo add serde.

We could possibly take this a step further to "all mutations" and include cargo update and cargo generate-lockfile.

This does not include a "pinning" status message at this time.

How to test and review this PR?

[rustbot]

r? @ehuss

rustbot has assigned @ehuss.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

• Owners of files modified in this PR: @ehuss, @epage, @weihanglo
• @ehuss, @epage, @weihanglo expanded to ehuss, epage, weihanglo
• Random selection from ehuss, weihanglo

[rustbot]

This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

[weihanglo]

Thanks!

View changes since this review

[weihanglo]

So when edition 2027 is out we'll need to update these snapshots?

[weihanglo]

linux x86-64 stable

---- ssh::invalid_key_error stdout ----
SSH_AGENT_PID=109572
running `/home/runner/work/cargo/cargo/target/debug/cargo fetch`

thread 'ssh::invalid_key_error' (109569) panicked at tests/testsuite/ssh.rs:372:10:

--- Expected
++++ actual:   stderr
   1    1 | [UPDATING] git repository `ssh://testuser@127.0.0.1:32773/repos/bar.git`
   2    2 | [ERROR] failed to get `bar` as a dependency of package `foo v0.1.0 ([ROOT]/foo)`
   3    3 | 
   4    4 | Caused by:
   5    5 |   failed to load source for dependency `bar`
          ⋮
   9    9 | 
  10   10 | Caused by:
  11   11 |   failed to clone into: [ROOT]/home/.cargo/git/db/bar-[HASH]
  12   12 | 
  13   13 | Caused by:
Error: m  14      -   [ERROR] SSH host key has changed for `[127.0.0.1]:32773`
  15      -   *********************************
  16      -   * WARNING: HOST KEY HAS CHANGED *
  17      -   *********************************
  18      -   This may be caused by a man-in-the-middle attack, or the server may have changed its host key.
       14 +   network failure seems to have happened
       15 +   if a proxy or similar is necessary `net.git-fetch-with-cli` may help here
       16 +   https://doc.rust-lang.org/cargo/reference/config.html#netgit-fetch-with-cli
  19   17 | 
  20      -   The ECDSA fingerprint for the key from the remote host is:
  21      -   SHA256:[..]
  22      - 
  23      -   You are strongly encouraged to contact the server administrator for `[127.0.0.1]:32773` to verify that this new key is correct.
  24      - 
  25      -   If you can verify that the server has a new key, you can resolve this error by removing the old ecdsa-sha2-nistp256 key for `[127.0.0.1]:32773` located at [ROOT]/home/.ssh/known_hosts line 1, and adding the new key to the `net.ssh.known-hosts` array in your Cargo configuration (such as [ROOT]/home/.cargo/config.toml) or in your OpenSSH known_hosts file at [ROOT]/home/.ssh/known_hosts
  26      - 
  27      -   The key provided by the remote host is:
  28      - 
  29      -   [127.0.0.1]:32773 ecdsa-sha2-nistp256 [..]
  30      - 
  31      -   See https://doc.rust-lang.org/stable/cargo/appendix/git-authentication.html#ssh-known-hosts for more information.
       18 + Caused by:
       19 +   failed to start SSH session: Failed getting banner; class=Ssh (23)

requeuing