"update plugin" context menu in the extension manager is not intuitive

[psifertex]

So the "update plugin" context menu does nothing unless you select a different version in the version list. This is not intuitive. That option should:

1. Only show up when you have an update and
2. Should update the plugin to the latest without making me select it from the version list.

Likewise, there's a few other related bugs features here:

1. "Change version" shows up in the extension manager when I have the same version selected which is clearly not the intended case:

If you press it, it will do absolutely nothing.

I think what we should do is remove the upgrade/downgrade button entirely. When the user selects a different version, simply pop up a dialog confirming whether they wish to upgrade or downgrade and then can either accept or cancel. No additional button is needed and then we can...

2. Add an "update plugin" button in the same spot where the previous button is that would behave the same as the context menu and actually just update the plugin.

[psifertex]

Should also check out #8502 when resolving this

[psifertex]

One problem with the above plan is that you can't browser previous readmes which is why the current behavior exists. I... think that's fine? 99% of the time people are just going to want to switch to the version, not explore previous readme states. So I'm fine with this proposal as is, but it's worth some discussion in case anyone disagrees.

[Calastrophe]

If this is getting reworked, I have some suggestions for making it intuitive:

Not Installed -> [Install]
Installed, no update, but enabled -> [Disable] [...]
Installed, no update, but disabled -> [Enable] [...]
Installed, needs updating, but enabled -> [Update] [Disable] [...]
Installed, needs updating, but disabled -> [Update] [Enable] [...]

The ... is the overflow and it holds options like: Switch version..., View version history, Reinstall, Uninstall.

The View version history is just an idea for the idea of browsing previous READMEs or understanding what the update actually provided.

I also think the current installed version and enabled/disabled status should be put above those buttons (either below or above the plugin tags). So it roughly looks like:

Update available · Disabled · Version 1.0.0:

[Update] [Enable] [...]

[psifertex]

Yeah, I like the idea of hiding the extra buttons under a sub-menu instead of reflowing the layout which is the current behavior.

I don't think view version history is the right call for that, I think just letting the user select the version and then cancelling the upgrade/downgrade dialog is in practice going to work better? But I'm not dead set on it.

[psifertex]

As for status, yeah we already have the tag/bubbles. "Update Available", "Deprecated", "Enabled", "Disabled" could all live there from a UI perspective. In fact, we already put "Deprecated" there as it is. It's the others that are left out.

Especially nice if you've collapsed the sidebar.

[Calastrophe]

I don't think view version history is the right call for that, I think just letting the user select the version and then cancelling the upgrade/downgrade dialog is in practice going to work better? But I'm not dead set on it.

I agree with that sentiment, I think Switch version..., Reinstall, Uninstall is enough in the overflow menu. I mostly just wanted to float the idea of seeing the developer-reported major changes between plugin versions, but in practice I don't see it being of much use.