Canary fails when a release is yanked

When we yanked release-2023-12-12, the canary still tried to run against that version and failed with:

```
2023-12-14T00:13:00.444756Z INFO Emitting metrics...
Error: Failed to cargo build:
Status: 101
Stdout:
Stderr: Updating crates.io index
error: failed to select a version for the requirement `aws-config = "^1.1.0"`
candidate versions found which didn't match: 1.0.3, 1.0.1, 1.0.0, ...
location searched: crates.io index
required by package `aws-sdk-rust-lambda-canary v0.1.0 (/home/runner/work/aws-sdk-rust/aws-sdk-rust/smithy-rs/tools/ci-cdk/canary-lambda)`
perhaps a crate was updated and forgotten to be re-vendored?
```

Start in smithy-rs/tools/ci-cdk/canary-lambda, the package named in the failure, and trace how the canary selects the release version. Reproduce the failed cargo build if possible and verify that a yanked release is no longer selected while the canary still builds successfully.

Written by the indexing model from the issue text.