Plugin deployment doc incorrectly claims that built-in napari plugin installer doesn't install from conda

[TimMonko]

🐛 Bug

Deploying plugin docs says that the napari plugin installer doesn't currently install from conda... but I'm pretty sure it does?

I broke a conda-forge-feedstock many versions ago, and never got around to figuring out how to make conda distributions actually work. Because of this note, I just assumed that conda didn't work in napari, but then I had a user report that my plugin looks way different than expected -- no surprise when it was nearly a year out of date in conda, and I naively just assumed pip was how people got the plugin. I think the installer defaults to conda now.

I'll try to improve the Deploying to Anaconda section as I figure things out. So that people like me don't give up like I did.

[Czaki]

You are right. The old bundle version was pip only, and we still have not updated part of docs.

[melissawm]

Updating the plugins docs is my priority for the next couple of weeks. There are several issues about this that I want to address and this is one of them. Thanks for the report!

[TimMonko]

Feel free to ping me to look things over. If I find some time, you can also let me any documentation I could work on. Right now I'm working back through thinking about my napari plugin since I've learned much in the past 2 years that I had originally just brute forced. (which I think was, at least, a good thing for getting users like me started!)