[ci] Review `cargo-semver-checks` Github Action workflows, find gaps related to feature resolution & re-exports of workspace dependencies

Context: https://github.com/awslabs/aws-lambda-rust-runtime/issues/1023

We had semver breakage in a `lambda_http` patch release due to its dependency on `aws_lambda_events`.

My understanding was that our CI should have failed this. We should find whether there is a gap in our CI setup, or a bug in `cargo-semver-issues`.

阅读链接的 issue #1023，并检查现有的 `cargo-semver-checks` GitHub Action workflows，重点关注 feature 解析和 workspace 依赖项的重新导出。复现或描述 `lambda_http` 和 `aws_lambda_events` 的 semver 破坏情况，并记录 CI 是否存在配置缺口，或者 `cargo-semver-issues` 是否存在 bug。

由索引模型根据 Issue 内容生成。