chore: stage minor version bump for lambda-events before next release

[jlizen]

📬 Issue #, if available:

✍️ Description of changes:

We are having persistent CI failures because our next aws-lambda-events release should be minor, not patch. Staging that change in tree now so that CI doesn't stay red until our next release.

--- failure struct_field_marked_deprecated: pub struct field is now #[deprecated] ---

Description:
A pub field of a pub struct is now marked #[deprecated]. Downstream crates will get a compiler warning when accessing this field.
        ref: https://doc.rust-lang.org/reference/attributes/diagnostics.html#the-deprecated-attribute
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.46.0/src/lints/struct_field_marked_deprecated.ron

     Summary semver requires new minor version: 0 major and 1 minor checks failed

Example: https://github.com/aws/aws-lambda-rust-runtime/actions/runs/22236953957/job/64350031058?pr=1102

🔏 By submitting this pull request

• I confirm that I've ran cargo +nightly fmt.
• I confirm that I've ran cargo clippy --fix.
• I confirm that I've made a best effort attempt to update all relevant documentation.
• I confirm that my contribution is made under the terms of the Apache 2.0 license.

[jlizen]

not strictly needed given cargo resolution, but less confusing

[jlizen]

Ah, apparently release-plz would trigger on this regardless. So we could bump the events for a release, but I'd rather do that with actual release notes and such.