Rust Toolchain: Upgrade to rust edition 2024

[eval-exec]

• rust-toolchain: Upgrade to 1.85.0
• clippy: apply clippy fix by cargo clippy --fix --all
• clippy: fix suspicious_doc_comments
• clippy: fix static mut warning: https://doc.rust-lang.org/nightly/edition-guide/rust-2024/static-mut-references.html
• Apply cargo fix --edition
• clippy: apply clippy::single_match
• Execute cargo fmt --all

[eval-exec]

Hello, @driftluo, Do I need to squash these 7 commits into 1 commit?

[eval-exec]

Squashed multiple commits into one commit.

[eval-exec]

@driftluo , we can delete these unstable cfg now:

tentacle/tentacle/src/builder.rs

Lines 359 to 360 in f685607

	#[cfg(feature = "unstable")]
	#[cfg_attr(docsrs, doc(cfg(feature = "unstable")))]

[driftluo]

@driftluo , we can delete these unstable cfg now:

tentacle/tentacle/src/builder.rs

Lines 359 to 360 in f685607

	#[cfg(feature = "unstable")]
	#[cfg_attr(docsrs, doc(cfg(feature = "unstable")))]

I personally think that the runtime needs to be unstable. There is no feedback from spawn yet, and the API cannot be guaranteed. It is also not possible to stabilize the API for the time being.

[eval-exec]

@driftluo , we can delete these unstable cfg now:

tentacle/tentacle/src/builder.rs

Lines 359 to 360 in f685607

	#[cfg(feature = "unstable")]
	#[cfg_attr(docsrs, doc(cfg(feature = "unstable")))]

I personally think that the runtime needs to be unstable. There is no feedback from spawn yet, and the API cannot be guaranteed. It is also not possible to stabilize the API for the time being.

Ok, I have reverted it.