chore(deps): upgrade rust to v1.93.1

[duncanista]

What?

Upgrade rust to latest stable 1.93.1

Why?

time vulnerability fix is only available on rust >= 1.88.0

[duncanista]

Eventually want to replace this with the propagator in dd-trace-rs

[duncanista]

Self-reviewed to not miss anything, mostly cargo clippy --fix

[duncanista]

Might need to be merged with the failing audit for now

[litianningdatadog]

Code review

Found 1 issue:

1. .unwrap() introduced in production code, violating the project's #![deny(clippy::unwrap_used)] rule (CLAUDE.md says: "Strict linting rules enforced (no clippy::unwrap_used, etc.)")

The change replaces unsafe { NonZero::new_unchecked(5) } with NonZero::new(5).unwrap(). While the .unwrap() is in a const context (making it a compile-time guarantee rather than a runtime panic), clippy::unwrap_used is enforced via #![deny(clippy::unwrap_used)] in lib.rs and fires syntactically regardless of const context. A safer alternative that satisfies both goals: keep unsafe { NonZero::new_unchecked(5) } with a // SAFETY: 5 is non-zero comment.

datadog-lambda-extension/bottlecap/src/appsec/processor/mod.rs

Lines 35 to 39 in eae57a3

	}
	impl Processor {
	const CONTEXT_BUFFER_DEFAULT_CAPACITY: NonZero<usize> = NonZero::new(5).unwrap();
	/// Creates a new [`Processor`] instance using the provided [`Config`].

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}