[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`.

Read the linked issue #1023 and inspect the existing `cargo-semver-checks` GitHub Action workflows, focusing on feature resolution and re-exports of workspace dependencies. Reproduce or characterize the `lambda_http` and `aws_lambda_events` semver breakage, then document whether CI has a configuration gap or `cargo-semver-issues` has a bug.

Vom Indexierungsmodell aus dem Issue-Text verfasst.