feat: support terminology codes

[cmdoret]

Summary

This adds support for terminology codes instead of free text for specific metadata fields, along with autocomplete suggestion in the terminal.

Currently, the following properties/terminologies are used:

• "cell_type": "https://purl.obolibrary.org/obo/cl.owl",
• "source_material": "https://purl.obolibrary.org/obo/uberon.owl",
• "taxon_id": "https://purl.obolibrary.org/obo/ncbitaxon/subsets/taxslim.owl"

Major changes

• Refactor CLI code: move prompt utilities to dedicated module (modos.prompt)
• Add code-matching module (modos.codes)
• Implement CodeMatcher protocol with two members (remote/local)
  • Remote is used if an endpoint is provided (completion runs on server, faster)
  • Local used as fallback (ontology downloaded and runs on client machine)
• fuzon-http service added as a service in modos server deployment
• pyfuzon added as extra dependency for local code matching

Trying it

To test local autocomplete in terminal:

modos create data/example
modos add data/example sample

To rely on the server for autocomplete:

make deploy
modos --endpoint=http://localhost create data/example
modos --endpoint=http://localhost add data/example sample

Notes

Codes are recommended based similarity between user input and labels, but only the URIs are persisted in metadata.

Follow up (separate issues):

• speed up download when using local completer
  • terminology caching (+async download in background)

Open questions

When creating a modos from input yaml (instead of interactively) (see data/ex_config.yaml), URIs are now required for the 3 properties above.

It may be painful for users to find out what URIs to input in the yaml. Should we provide some kind of subcommand just to get the codes (basically a fuzon wrapper)?
Perhaps something along the lines of this

# modos codes <property> <query>
modos codes cell_type "red blood cell"

[cmdoret]

TODO: clone release instead of branch, once PR is merged