Fix #334, Add Functional Tests Step to CI

[ArielSAdamsNASA]

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 #334

Testing performed
Tested on fork repo.
Deprecated Build, Test, and Run: https://github.com/ArielSAdamsNASA/cFS-JSF-Rules/actions/runs/1198344779
Build, Test, and Run [OMIT_DEPRECATED=true]: https://github.com/ArielSAdamsNASA/cFS-JSF-Rules/actions/runs/1198344780
Also seen in checks in this PR.

Expected behavior changes
Build, test, and run workflows runs functional tests. Uses cache to reduce build time.

Contributor Info - All information REQUIRED for consideration of pull request
Ariel Adams, ASRC Federal

[skliper]

Looks like 4 jobs that really could be consolidated? Build, make test, then run with the functional test app. Or if these really need to be separate could the build be archived so it doesn't actually need to be built 4 times? Currently may be burning a lot of minutes w/ the duplicated work (especially since this is matrixed).

[astrogeco]

I'm fine with the separate jobs. We can figure out how to reuse the build files using cache. The one thing i would add is a dependency between run and functional test so that we don't even try to run the functional tests if plain run ./core-cpu doesn't work