spin plugins upgrade -v does not work for latest plugin version

[itowlson]

$ spin plugins update
Plugin information updated successfully

$ spin plugins list
js2wasm 0.1.0
js2wasm 0.2.0
js2wasm 0.3.0
js2wasm 0.4.0 [installed]
py2wasm 0.1.0 [installed]
py2wasm 0.1.1
py2wasm 0.2.0

$ spin plugins upgrade py2wasm -v 0.2.0
Error: plugin 'py2wasm' not found at expected location /home/ivan/.local/share/spin/plugins/.spin-plugins/manifests/py2wasm/py2wasm@0.2.0.json: No such file or directory (os error 2)

$ ls -1 /home/ivan/.local/share/spin/plugins/.spin-plugins/manifests/py2wasm/
py2wasm@0.1.0.json
py2wasm@0.1.1.json
py2wasm.json        # the culprit!

Why does this matter? Well, maybe it doesn't. If you want the latest version, save yourself some keystrokes and skip the -v. But it is a funny little inconsistency.

(The reason I came across this was planning for what I needed to do if the upgrade badger wanted to seek out the "last compatible" or "last in your major version" versions, rather than just "most recent or nothing." For my own laziness purposes, I was planning to construct the "how to upgrade" instruction to always display the -v. But this behaviour means I would have to construct the command differently for the truly latest version. Which is not a problem, just a quirk.)

[itowlson]

Apparently this got fixed somewhere along the line. Good times