Add benchmark workflow

[reyhankoyun]

Issue #, if available:

Description of changes:
This PR builds off of PR #122 and creates a benchmark workflow similar to integration tests workflow that runs the benchmarks added in PR #122

Add two basic benchmarks

• One that performs cache hit retrievals
• One that intentionally yields cache misses on every retrieval

Using criterion (used by the AWS SDK for Rust).

This hopefully will serve to catch performance regressions in future code changes and open the door to profiling.

Successful run from fork: https://github.com/reyhankoyun/aws-secretsmanager-agent/actions/runs/20082405961/job/57612354790

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.14%. Comparing base (7c6a7bc) to head (bb9e1f6).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #153      +/-   ##
==========================================
+ Coverage   91.88%   92.14%   +0.25%     
==========================================
  Files          14       14              
  Lines        2404     2405       +1     
  Branches     2404     2405       +1     
==========================================
+ Hits         2209     2216       +7     
+ Misses        147      143       -4     
+ Partials       48       46       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[simonmarty]

It looks like the upload is not succeeding with

Warning: No files were found with the provided path: aws_secretsmanager_caching/target/criterion/. No artifacts will be uploaded.

[ThirdEyeSqueegee]

The Criterion book has a section about benchmarking async functions. Did we take this into consideration when writing these tests? Not sure how it plays with Tokio.

[reyhankoyun]

The Criterion book has a section about benchmarking async functions. Did we take this into consideration when writing these tests? Not sure how it plays with Tokio.

Yes, we're already implementing Criterion's async benchmarking pattern for Tokio.