Ability to ignore a specific app update version

[!TIP]

Help move this idea forward

• Use the 👍 reaction to show support for this feature.
• Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
• Subscribe to receive notifications about status changes and new comments.

Is your feature request related to a problem? Please describe.

Sometimes app updates are released that are broken in some way. For example, nextcloud/flow#129, nextcloud/flow#130 make me not want to update this app to 1.3.0.

Therefore, I want to ensure that other admins on my instance do not accidentally accept this particular update either.

Describe the solution you'd like

A button in the app updates view (i.e. /index.php/settings/apps/updates) that allows me to ignore a single version. When the app is updated again, and a new version is the latest, the update should be offered again.

Describe alternatives you've considered

A more advanced version of this feature: "ignore this minor version", etc. But seems too complicated and like it would require a bunch of design work, for little benefit (see below).

Another alternative: make this problem unnecessary, by simply aggressively yanking app versions known to be broken in some way from the app store. But this seems a) unreliable given the volunteer nature of many Nextcloud apps' maintenance, and b) like a bad idea, since in a decent number of cases the decision is going to be site-specific anyway. Take nextcloud/flow#129 (linked above) for example - if you do not use Deno scripts, and do not use CORE:LISTEN_TO_EVENT, then this is probably not a breaking bug for you.

Additional context

None

Start at the app updates view at /index.php/settings/apps/updates and trace how available app versions are presented and accepted. Define how one version is ignored and how a later latest version becomes offered again, then add coverage for both behaviors using the existing update flow tests.