Update setup instructions

[mkcor]

Do we want to 'port' datacarpentry/image-processing#342 here? I would think so, since this change applies to what we are developing here, i.e., a Carpentries lesson in Python.

[tobyhodges]

I agree that pivoting to Miniforge is sensible here too. But the Figshare link will need to be replaced with some other solution for providing example data and an environment.yml file. Given that we have not yet chosen example data/narrative for the lesson, I suggest this can wait for the time being.

[Edit: re-reading this, it seemed like I was suggesting we need to use something other than Figshare, which was not what I meant. Figshare may still be the appropriate solution (unless a bioimage-specific repository is available?) but we will need to make a separate entry for the example data and environment description for this lesson.]

[marcodallavecchia]

Thank you for bringing this up @mkcor! I agree we should definitely port this change, but as @tobyhodges mentioned, it makes sense to wait for it to see which data (and final package list) and sharing platform we will be using.

In my opinion, it might even make sense to migrate entirely to UV, as it seems to be climbing up to being the new 'state-of-art' for virtual environment installations and it's so much faster (which could help for larger dependencies as we discussed with the inclusion of Napari and BioIO).

[mkcor]

@tobyhodges sure, that makes sense!

(unless a bioimage-specific repository is available?)

There's the IDR, which I know thanks to @joshmoore. I guess we could have 'data download' instructions where learners get the data from the IDR... This would correspond to real-world practice.