Install CI pipeline

[meowsbits]

trafficstars

Drafting CI pipeline installation.

As-is, the change set includes two pipeline options; only one is necessary. We can have a discussion comparing these options (Github vs. Azure), or alternatives, and then remove or change to use only what seems optimal and necessary.

Both pipelines build the llc executable and archive it as a .zip, retaining the artifact.

Latest builds on my personal fork, for reference:

• https://github.com/meowsbits/evm_llvm/actions/runs/103701569
• https://dev.azure.com/isaaca0624/isaaca/_build/results?buildId=7&view=results

Next steps for the CI pipeline could be discussed and implemented here, or in a following one or few PRs. These would probably include, but may not be limited to:

• [ ] Add testing to the pipeline as a predicate for building.
  • [ ] Linting?
• [ ] Automated Github Release drafts including the manufactured archives.
• [ ] Current builds are only provided for Ubuntu. I'm not sure what the limits of the program are, but I expect we can expand this to cover other wanted OSes as well.

Pending:

• [ ] Minor tweaks to the configs to modify parameters using my personal fork to using the upstream repo.
  • [ ] If Azure, possibly setting up the necessary Azure entities and permissions. (Github, I think, is plug-n-play.)
• [ ] Git hashes and/or tags are nice to have in the archive names.