testing of caching

[raynatopedrajeta]

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[jagpreetsinghsasan]

@raynatopedrajeta please use your fork to do this testing. (If the job is getting skipped, you can either investigate on the when condition of it {longer} or straightaway remove the when condition.)
Also for such testing it is better to remove all the jobs from the github workflow folder and only have those 2 jobs which you need to test. In that way, a lot of computational resources are saved.