feat: Add Edition2024

[Muscraft]

RFC for Edition2024. While the RFC is not yet merged, this follows rustc which added the 2024 edition previously in rust-lang/rust#94461

This PR adds Edition2024 as a possible value for edition = "xxxx". I did this by following the guide here.

[rustbot]

r? @weihanglo

(rustbot has picked a reviewer for you, use r? to override)

[Muscraft]

No tracking issue has been created yet, so this will have to be updated to include a link when the RFC gets merged and a tracking issue gets created.

If there is a tracking issue for cargo and rust, both links should probably be included.

[Muscraft]

While there currently is rust_2024_compatibility lint group, I set it to false as there are no lints in the group currently (from what I can tell). This was how Edition2021 originally was before it was updated to be true.

[epage]

@bors r+

[bors]

📌 Commit b3481b7 has been approved by epage

It is now in the queue for this repository.

[bors]

🔒 Merge conflict

This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.

How do I rebase?

Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

1. git checkout edition-2024 (switch to your branch)
2. git fetch upstream master (retrieve the latest master)
3. git rebase upstream/master -p (rebase on top of it)
4. Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
5. git push self edition-2024 --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.

Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.

Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message

Auto-merging src/cargo/util/toml/mod.rs
CONFLICT (content): Merge conflict in src/cargo/util/toml/mod.rs
Automatic merge failed; fix conflicts and then commit the result.

[epage]

@bors r+

[bors]

📌 Commit b2b3cfa has been approved by epage

It is now in the queue for this repository.

[bors]

⌛ Testing commit b2b3cfa with merge d74bc47...

[bors]

☀️ Test successful - checks-actions
Approved by: epage
Pushing d74bc47 to master...