Basic actions

[marnovandermaas]

These actions should help keep the legacy software and simulator in a buildable state.

You can see both of them passing here: https://github.com/marnovandermaas/sonata-system/actions

[HU90m]

I was planning to set up a nix based workflow similar to https://github.com/lowRISC/symphony-system/blob/9a502baeecd36002e0d4413bc7d63f9be5676709/.github/workflows/quality.yml

Mainly because:

• We can ensure the CI checks are super easy to reproduce locally and run before committing a PR.
• We'll also be using nix cache for the CHERIoT toolchain anyway)
• We'd like to move to pomona as a hosted runner and moving nix builds is trivial. (Also no rebuild required if it has been build before by CI or a lowRISC engineer has pushed to the cache.)

[marnovandermaas]

I was planning to set up a nix based workflow similar to https://github.com/lowRISC/symphony-system/blob/9a502baeecd36002e0d4413bc7d63f9be5676709/.github/workflows/quality.yml

Mainly because:

* We can ensure the CI checks are super easy to reproduce locally and run before committing a PR.

* We'll also be using nix cache for the CHERIoT toolchain anyway)

* We'd like to move to pomona as a hosted runner and moving nix builds is trivial. (Also no rebuild required if it has been build before by CI or a lowRISC engineer has pushed to the cache.)

I'm happy with that flow. I just put this PR together since it was quite easy and we can have some small checks on PRs until you get that set up.

outdated