Adding Recipe Management

[JanPeterDatakind]

Recipe Managers can now check out recipes from the db into a docker container, connect the container to their IDE, run, debug, and edit the recipe code, update other information about the record such as the intent, then check them back into the database.

[dividor]

Hi @JanPeterDatakind,

I started running locally, great stuff!

I checked in a change to merge recipes-creation into recipes-management, one less container. I also removed the VS Code container as a requirement, instead instructing that the user can exec into a the management container, or simply run with: docker exec haa-recipe-manager python recipe_sync.py --check_out <YOUR NAME>. More advanced users can configure remote containers, but I felt this was more consistent for now and reduced complexity a little.

A few feedback items on the PR as follows:

1. Let's import skills.py from the parent rather than copy into each recipe

2. Please fix the bug that creates multiple main calls on checking in/out

3. Remove any code which calculates embeddings and the python modules needed for that. See memory.py for examples

4. Fix failed code checks in Github actions (ensure pre-commit hooks are active)

5. Let's remove legacy recipes in the demo data and only have recipes using new format

6. Add two line breaks after boiler-plate code to import modules, and recipes code. Easier to read

[dividor]

Thanks for responding to the requested feedback items @JanPeterDatakind. I will now merge this PR, noting that additional work around simplifying user experience for creating recipes will be tracked under a new PR.