Add Aleo instructions

[d0cd]

This PR adds Linguist support for Aleo instructions, the format recognized and executed by the Aleo Virtual Machine (AVM). The AVM is a virtual machine with built-in cryptographic primitives for creating and verifying zero-knowledge proofs.

References

• Aleo
• Developer Documentation

Checklist

• [x] I am adding a new language.
  • [x] The extension of the new language is used in hundreds of repositories on GitHub.com. https://github.com/search?q=path%3A*.aleo+aleo+NOT+owner%3AProvableHQ++NOT+owner%3AAleoNet+NOT+is%3Afork&type=code. Note that a file is expected to occur once per repository, which meets the requirements outlined here.
  • [x] I have included a real-world usage sample for all extensions added in this PR. They are covered under the license that is tagged at the top of each file.
  • [x] I have included a syntax highlighting grammar: https://github.com/ProvableHQ/aleo-linguist/blob/master/syntaxes/Aleo.tmLanguage.json
  • [x] I have added a color
    • Hex value: #154bf9
    • Rationale: These are the brand colors.

[d0cd]

Hi @lildude! Do you have any feedback on this PR? Happy to incorporate any suggestions to make it more reviewable.

[lildude]

The extension of the new language is used in hundreds of repositories on GitHub.com. https://github.com/search?q=path%3A*.aleo+aleo+NOT+owner%3AProvableHQ++NOT+owner%3AAleoNet+NOT+is%3Afork&type=code. Note that a file is expected to occur once per repository, which meets the requirements outlined https://github.com/github-linguist/linguist/issues/5756.

That restriction is for cases of only one file per repo. A quick look at a few of the search results shows it's very common for repos to contain more than one .aleo file, commonly in an imports directory.

This means things are a long way from reaching the usage requirements.