Updating cache package

[vrundakansara]

Description

Email from GitHub marketing:

Starting February 1st, 2025, we are closing down v1-v2 of actions/cache (read more about it in this changelog announcement) as well as all previous versions of the @actions/cache package in actions/toolkit. Attempting to use a version of the @actions/cache package or actions/cache after the announced deprecation date will result in a workflow failure. If you are pinned to a specific version or SHA of the cache action, your workflows will also fail after February 1st.

What you need to do:
We strongly encourage you to update your workflows to begin using a supported version of actions/cache, and upgrade your actions or other products that depend on the @actions/cache package to 4.0.0 or above.

Supported versions and tags:

actions/cache:

actions/cache@v4
actions/cache@v3
actions/cache@v4.2.0
actions/cache@v3.4.0

Cached entries within their retention period will remain accessible from the UI or REST API regardless of the version used to upload.

Types of changes

Dev Dependencies - Package Update

How has this been tested?

Test if the associated pipelines pass or not.

Checklist:

• My code is tested
• My code passes the PHPCS tests
• I've created the npm build.
• My code follows accessibility standards
• My code has proper inline documentation
• I've included any necessary tests
• I've included developer documentation
• I've added proper labels to this pull request