Fix #621, update action versions to v3

[jphickey]

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
Update cache, checkout, and upload-artifact actions from v2 to v3. Should be a drop-in replacement and removes a warning about node.js 12 deprecation.

Fixes #621

Testing performed
Run all github workflows

Expected behavior changes
No more warnings about node.js 12 deprecation

System(s) tested on
Github hosted runner

Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

[ArielSAdamsNASA]

@jphickey Looks good, but I don't see where the node.js warning is removed. For example, click the Format Check workflow triggered by this PR and take a look at the workflow file. It uses v3, but the warning is still there. Here is a link: https://github.com/nasa/cFS/actions/runs/3535753791

[jphickey]

@jphickey Looks good, but I don't see where the node.js warning is removed. For example, click the Format Check workflow triggered by this PR and take a look at the workflow file. It uses v3, but the warning is still there. Here is a link: https://github.com/nasa/cFS/actions/runs/3535753791

Thanks for catching that, it looks like the warning in that particular run was from the 3rd-party action "gsactions/commit-message-checker@v1", not the github actions that were updated in this PR.

We'll need to see if there is an update/new version from the original author. I'll check that. I'd still recommend merging this PR, as it fixes most of them - there may be some left but I can take care of those as they appear.

[jphickey]

I checked and yes, the "commit-message-checker" does have a version 2 now. So I pushed another commit (see 5a1174f) that updates this action from v1 to v2 and the warning is gone. See https://github.com/nasa/cFS/actions/runs/3593359346.

We will just have to keep an eye out for remaining deprecation warnings and watch for new versions of whatever action is triggering them. Problem is when there are a lot, things get buried, so even if this may not fix 100% of the warnings, it will make the remaining ones easier to spot and fix.