`tap package download`/`install` should use the version specified and return error if not found

Today you might get e.g. 1.4.0 installed if you specified --version 1.5 but no 1.5 exists.

added CLI Package Manager Usability labels

changed the description

changed milestone to %9.10

added Strech Goal label

assigned to @alexnlarsen

This is pretty much a duplicate of #341 (closed)

mentioned in issue #259 (closed)

added flow::In Progress label

mentioned in merge request !632 (merged)

This turns out to only be the case if you use --force. After some discussion, we decided that that is not intended. If you wanted to allow other versions, you can use --version Any.

We should change --force to not implicitly also mean --version Any.

added flow::Merge Requested label and removed flow::In Progress label

closed with merge request !632 (merged)

mentioned in commit 2422e43e

Fixed. Verified on 9.10.0-beta.29

Verified for both download and install

added QA Verified label

changed title from tap package doanload/install should use the version specified and return error if not found to tap package download/install should use the version specified and return error if not found

changed the description

mentioned in merge request !642 (merged)

changed title from tap package download/install should use the version specified and return error if not found to {+tap package download/install+} should use the version specified and return error if not found

changed title from tap package download{-/-}install should use the version specified and return error if not found to tap package download{+/+}install should use the version specified and return error if not found