Question about Github Actions: Adding Caching?

### Description

I happen to come across this article: https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows. Looking at the current GitHub actions workflows, it seems that none of the workflows utilize caching.

Some snippets from the article:

Workflow runs often reuse the same outputs or downloaded dependencies from one run to another. For example, package and dependency management tools such as Maven, Gradle, npm, and Yarn keep a local cache of downloaded dependencies.

Jobs on GitHub-hosted runners start in a clean runner image and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. To help speed up the time it takes to recreate files like dependencies, GitHub can cache files you frequently use in workflows.

Would this be something that would benefit our workflows?

Review the repository's current GitHub Actions workflows and compare their dependency-install steps with GitHub's caching documentation. Determine whether caching is beneficial, identify the workflows affected, and define how a change would be verified.

Written by the indexing model from the issue text.