Add GHA yocto workflows for common device types

[klutchell]

These workflows are for testing the build steps only.

Change-type: patch

---

Contributor checklist

• Changes have been tested
  • Covered in automated test suite
  • Manual test case recorded
• Change-type present on at least one commit
• Signed-off-by is present
• The PR complies with the Open Embedded Commit Patch Message Guidelines

Reviewer Guidelines

• When submitting a review, please pick:
  • 'Approve' if this change would be acceptable in the codebase (even if there are minor or cosmetic tweaks that could be improved).
  • 'Request Changes' if this change would not be acceptable in our codebase (e.g. bugs, changes that will make development harder in future, security/performance issues, etc).
  • 'Comment' if you don't feel you have enough information to decide either way (e.g. if you have major questions, or you don't understand the context of the change sufficiently to fully review yourself, but want to make a comment)

[vipulgupta2048]

What's the benefit of doing genericx86-64 and intel-nuc here on meta-balena again? Are we completing the checklist or actually testing new functionality

[klutchell]

What's the benefit of doing genericx86-64 and intel-nuc here on meta-balena again? Are we completing the checklist or actually testing new functionality

Just completing the checklist, I don't expect to discover any new issues here except we can test without deploys on this repo.

[lmbarros]

Looks good. Small differences from what I was using on my fork (no deploys, use "this" meta-balena branch), all of which seem to make sense for meta-balena testing.