Discovery: eDSL Syntax Requirements, Naming, Structure

[kjam]

We should set up at least one discovery call and follow up with work on design documents around how our eDSL should function. This also means thinking about how Python is used directly with the runtime as well as via PyCape.

Currently, the methods are outlined here: https://github.com/tf-encrypted/runtime/blob/main/moose/edsl/base.py

And the pymoose functionality is here: https://github.com/tf-encrypted/runtime/tree/main/rust/pymoose

There are also notes on comparable libraries here: https://docs.google.com/document/d/1Vt-8DOygykpRfFKlPnvpr5l5VBvnsQgrcoFVTXibx5w/edit?usp=sharing

To close this ticket we need to:

• Evaluate and formalize the DSL with attention to something manageable for the initial release
• Document initial eDSL for release (documentation and examples first!)
• Create new tickets in pyCape for how to both (a) organize pyCape repository to be more OS friendly and (b) support creating custom computations for data scientists directly in pyCape

[kjam]

We likely want to think about if things like https://github.com/capeprivacy/cape-worker/issues/209 should be pulled into this planning and properly addressed.

@jvmncs and @yanndupis - Please link anything that should also be taken into account as we do the planning :)