Housekeeping: doc update, release, codecov, templates

[constantinpape]

• Update the developer documentation to reflect new plugin design
• Add BAND to the doc. (Formulating this more general for future services like KissKI or BioEngine)
• Figure out what's going on with codecov, see Codecov report uploads not working #234.
• Create an FAQ for the Documentation, to address common installation and performance issues, see Add FAQ section #511
• Create issue (referencing FAQ) and PR templates (referencing the new Contributing section).
• Explain cache folder in doc, see Use a consistent cache directory #268
• Add zenodo locations to the doc (after new versions of generalist models)

[GenevieveBuckley]

Add BAND to the doc. (Formulating this more general for future services like KissKI or BioEngine)

PR #250 might help with the first part of this (but not KissKI or BioEngine)

[claydugo]

This is pointing the readme to docs/ instead of the actual directory doc/ FYI

[constantinpape]

Hi @claydugo ,
I am not quite sure what you mean by your commen. Where do we point to docs instead of doc?
Thanks!

[claydugo]

In the README for the contributing and developer documentation links.

[anwai98]

• Adding PyTorch / CUDA Toolkit minimum version requirements (or tested ones) somewhere in the documentation (for finetuning and features requiring PyTorch) (?)

EDIT: Taken care of in FAQs.

[anwai98]

Generating and uploading our micro-sam package to PyPI (heard some interests on this)

Edit: Hmm, now that I think about it, wouldn't be feasible because of vigra and nifty.

[anwai98]

• Update micro-sam in BAND:
  • Update the logo
  • Update the name: "usam" -> "µsam"
  • Support the latest release (1.0.0 - as of 03.05.2024)