Fix #858, Use Unique Cache Keys for Workflow Reruns

[arielswalker]

Checklist (Please check before submitting)

• I reviewed the Contributing Guide.
• I signed and emailed the appropriate Contributor License Agreement to GSFC-SoftwareRelease@mail.nasa.gov and copied cfs-program@lists.nasa.gov.

Describe the contribution
Fixes #858

Testing performed
Build, Test, and Run [OMIT_DEPRECATED = false] Run 1 - Cache Key: deprecated-build-16353548187-1-release
Build, Test, and Run [OMIT_DEPRECATED = false] Run 2 - Cache Key: deprecated-build-16353548187-2-release
Build, Test, and Run [OMIT_DEPRECATED = true] Run 1 - Cache Key: build-16353548197-1-release
Build, Test, and Run [OMIT_DEPRECATED = true] Run 2 - Cache Key: build-16353548197-2-release
cFS Documentation and Guides Run 1 - Cache Key: cfs-doc-16353548233-1
cFS Documentation and Guides Run 2 - Cache Key: cfs-doc-16353548233-2

Expected behavior changes
github.run_number uses a unique number per workflow file, but it does not change on re-runs of the same workflow run and is not unique per run. github.run_id is a a globally unique identifier for a specific run of a workflow. github.run_attempt increments each time a workflow is rerun. Using both github.run_id and github.run_attempt will provide a unique key for any workflow run.

System(s) tested on
GitHub Actions

Contributor Info - All information REQUIRED for consideration of pull request
Ariel Walker, MCSG TECH