Tracker: FlatGFA Python bindings

[sampsyo]

Here's just a snapshot of some next steps for the Python bindings.

Project infrastructure:

• CI. Add tests for FlatGFA Python bindings #178 added some tests; they should run in GitHub actions. Maturin has a generate-ci command that should help with this. Try setting up CI for Python bindings tests #180
• Build docs. Just like we have auto-published Sphinx docs for mygfa, let's do the same for the FlatGFA module. Start docs for FlatGFA Python bindings #181
  • Expand/improve docs: at least divide into a few top-level sections. Python types and expanded docs #182
• Publish on PyPI. I believe Maturin/Actions can help with this too.

API "surface area":

• Mutation. Let's make it possible to build up a graph from scratch.
• Expose the ops. Things that are currently CLI subcommands (in cmds.rs) should be put into a library of useful "ops" on the GFA data structure. This way, you can string together multiple operations in a Python invocation. In the limit, maybe we can reproduce odgi pipelines from our collaborators as Python scripts.

Python niceties:

• The various objects should probably be made equatable/hashable. Strings and equality for FlatGFA Python objects #183
• Use str(obj) on paths, links, steps, etc. to produce GFA string fragments. Strings and equality for FlatGFA Python objects #183
• Names (of paths) should probably by str and not bytes? Seems fine to assume these are UTF-8. Nucleotide sequences can stay bytes. Strings and equality for FlatGFA Python objects #183
• Add typing hints. These would be especially helpful for the docs. Python types and expanded docs #182

[sampsyo]

It's on PyPI (and therefore pip installable) now: https://pypi.org/project/flatgfa/