Migrate from Go to Erlang NIF

[oubiwann]

This work will take place in a separate branch, based off of the latest release branch. If the work is successful and preferred to the Go solution, it will become the next release branch.

High-level tasks that need to be completed first include:

• Create new epic branch
• Update CI/CD with the latest and ensure that current code still works
• ❌ Determine workflow for using rustler in an LFE/rebar3 project geomyidia/midiserver#40
  • Does the rebar3 plugin support rustler-precompiled?
• ❌ Explore the process of creating an Erlang API wrapping Rust bindings with Rustler, e.g.:
  • https://medium.com/@brucifi/writing-your-first-erlang-nif-in-rust-274374094207
  • https://github.com/haubie/midiex/blob/main/lib/midiex/backend.ex
• Explore using the C++ MIDI NIF for Erlang that's used by the Sonic Pi project geomyidia/midiserver#41

Lower-level tasks:

• Determine if erlsci/midilib will still be used, and if so, if it needs to be updated geomyidia/midiserver#43
• Update deps, etc.
• Remove all old code referencing midiserver, Go, erlexec, etc.
• Refactor undermidi for the Erlang NIF #56
• Create a high-level API that uses midilib's midibinfor writing directly to MIDI devices #57
• Come up with some testing MIDI sequences #58
• Define LFE/Erlang wrapper API #53
• Allow for more control over interaction with system MIDI #59

Enhancements/cleanup:

• When using the rebar3 profile + alias rebar3 as undermidi repl, ensure that undermidi is started automatically
• When starting undermidi automatically (or with that repl alias), replace the LFE banner with the undermidi one

Final epic tasks:

• Update LICENSE with notes about pulled in software (Sonic Pi Erlang, C/C++, etc.)
• Update copied files with file header comments for attribution/license
• Evaluate effort for level of success/future viability
• Create new repo for old code, e.g., midiserver-go, and push main there for easy reference/use
• Update logo (Liffybot?!), merge epic to main, cut release, push to hex.pm