Bug: cache push and pull in case of ci_job should be avoided as it doesn't make sense in case of ci_job, or we can make it env driven

[prakash100198]

📜 Description

cache push and pull in case of ci_job should be avoided as it doesn't make sense in case of ci_job, or we can make it env driven

👟 Reproduction steps

1. make a ci_job and trigger that job
2. it will now produce cache and will push the cache in the desired blob configured

👍 Expected behavior

skip cache push pull in this particular case

👎 Actual Behavior

cache is getting pulled and pushed , but cache in this case is useless

☸ Kubernetes version

1.30

Cloud provider

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct