[ENH] Rust<>Python proxy calls back into python

[HammadB]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • /
• New functionality
  • Proxies all calls via the bindings back into the python code
  • Some calls are left not going through rust just to make the PR smaller, will stub out the rest, it is functionally the same
  • This is just to allow testing to be green while we convert to the rust based impls

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

None

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[codetheweb]

I don't think tests will pass without stubbing out the rest of the API, but that's fine, I can do that in my testing PR or we can do it separately

[HammadB]

All of the methods are stubbed, they proxy back into python, or just never go into rust but still proxy - I don't follow

[codetheweb]

my bad, sorry--misread the implementation
makes sense to me 👍