[TECHNICAL DEBT] Split Ares into two parts, project_ares and ares_lib

[bee-san]

Why?

Ares is made up of 2 parts:

1. The CLI
2. The Library

If someone wants to use the library they would need to import the CLI stuff too. It is a good idea to make the CLI a different app and make it call the library, rather than have them both bundled into one.

[bee-san]

We can do this using Cargo Workspaces https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html

[bee-san]

I am working on this!

So far I have split Ares into two, but I need to rename the packages and make sure that the CLI can use the library.

Our workflow will be a bit weird. Our CLI will only update if we push an update to its cargo.toml updating the library.

Good news is that we can update the library with breaking changes without breaking the CLI, slightly sad news is that our release.yml GitHub action will break.

However I am reading this blog post:
https://blog.axo.dev/2023/02/cargo-dist

Which talks about a nice way to distribute Cargo projects using CI and I think we should switch to it. My instinct is to:

• Break our packages into two
• Delete the old CI and go back to manual for now
• Write a new release CI with cargo-dist

This will also mean we can automatically distribute .exe for windows too