Add BeeAI Backend

[rockenman1234]

Hey y'all!

I hope you're doing well - I've managed to get a working version of Mellea and BeeAI up and running! This needs more testing, and feedback - but it seems like it's ready for a review. See below for a screenshot of the test file I wrote:

I tried to follow the open issue listed here: #19 - but I'm pretty sure I might've missed something so, your feedback is very welcome! BeeAI doesn't support python 3.10, it needs 3.11 or better - so I've updated the code to reflect that change.

I think I've also got most things documented here on this markdown file.

Thanks for your time! :-)

[nrfulton]

Thanks, @rockenman1234! This is fantastic work.

We've been thinking a lot about how the integration between Mellea and GUIs (including Bee Platform) should work. Our current thought is that we should add event streams to MelleaSession, and that GUIs should be implemented by listening to those streams. This has some implications for your PR. I suspect that a lot of what you're doing via Backend subclassing would instead be done by a Session listener. (I could be wrong -- I'll take a closer look on Friday.)

Let me know if you'd like to join a design meeting regarding this and a big basket of other related things. I left a bread crumb at #103 (comment) intended specifically for you.

I'm sorry for not updating #19 as that vision has evolved. The upside is that your code is super well-written and addresses all of the essential stuff implied by #19. So we'll eventually be able to merge your code regardless of the path forward. (And we'll of course take on that work if you lack bandwidth!)

[rockenman1234]

@nrfulton Yes sir, no worries at all!

I completely understand that this is y'all’s baby, and I don’t want to step on any toes. I’m just glad to hear you were pleased with my work! I’d be more than happy to join in and contribute wherever I can. After seeing Mellea in person last week at GT, I really liked the vision and would love to help push it forward.

Please feel free to share any feedback - I’ll plan to update the PR in about a week once you're done (though of course others are welcome to jump in sooner if they’d like to move things along). I really like the idea of building the same AI app across multiple platforms with multiple providers, and having some way to ensure the outputs are reasonable. Over the summer I worked quite a bit with the BeeAI platform and framework, so I think I’m familiar enough to be useful here.

I’d also love to join any meetings whenever possible! Please feel free to follow up by email (kjenkins60@gatech[dot]edu) and I’ll be glad to share my schedule. My Apologies about the code dump - totally get it's a lot to read and process, so please take your time. I personally felt that getting the CI/CD pipe just right was probably the hardest part of this whole thing, since every darn system is different from the last I've used!

Also, no offense intended at all - but it might be helpful to add a Code of Conduct and Contribution Guide to the to-do list. 😅

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 Enforce conventional commit

This rule is failing.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?: