Add Validate Templates (#2387)

[rlcheng]

• Add validate_templates.yml and support expect scripts.

Related Issue(s)
Has Unit Tests (y/n)
Documentation Included (y/n)

---

Change Description

A description of the changes contained in the PR.

Rationale

A rationale for this change. e.g. fixes bug, or most projects need XYZ feature.

Testing/Review Recommendations

Fill in testing procedures, specific items to focus on for review, or other info to help the team verify these changes are flight-quality.

Future Work

Note any additional work that will be done relating to this issue.

[thomas-bc]

This is really neat! 🚀

One question: do we want to have this workflow run on the devel state of fprime-bootstrap and fprime-tools ?
This would allow us to validate that we are keeping bootstrap/tools in sync with the devel version of F Prime. It could match the process in the tutorials tests, see e.g.

fprime/.github/workflows/ext-build-hello-world.yml

Lines 18 to 22 in 0e4b4c2

	get-branch:
	name: "Get target branch"
	uses: ./.github/workflows/reusable-get-pr-branch.yml
	with:
	target_repository: fprime-community/fprime-tutorial-hello-world

This has been a pretty successful process for the tutorials so far.

[LeStarch]

Released fprime-bootstrap should work on the latest release.

devel fprime-bootstrap and devel fprime-tools should work with devel fprime. No?

[thomas-bc]

Yes, they should. But we can't confirm that they actually do unless we check it in CI. I am suggesting we should do that, following the same pattern that we use on our tutorial repositories.

e.g.

pip install git+https://github.com/nasa/fprime-tools@{devel,pr-xxxx} // and bootstrap
fprime-bootstrap project
git clone https://github.com/nasa/fprime      // use fprime@devel in the new project
fprime-util build
fprime-util new --deployment
cd MyDeployment
fprime-util build

This validates that the latest devel of fprime, fprime-tools and fprime-bootstrap are all in sync.

Or am I missing your point?