[BUG] Swatinem is considering all rust related ENVs for cache key calculation

[hrithikesh026]

Bug Description

since the rust and cargo ENVs are different in PUSH and PR workflows, it causes the cache key to be different in both even though no changes are made to cargo.lock and cargo.toml files

Expected Behavior

cache key remain same if cargo.toml doesn't change.

Actual Behavior

cache key depends on env changes.

Steps To Reproduce

Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'

Context For The Bug

No response

Environment

Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the x-request-id response header to help us debug your issue.

If not (or if building/running locally), please provide the following details:

1. Operating System or Linux distribution:
2. Rust version (output of rustc --version): ``
3. App version (output of cargo r --features vergen -- --version): ``

Have you spent some time checking if this bug has been raised before?

• I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit a PR?

Yes, I am willing to submit a PR!