ENT-14170: Fixed updating to a pinned module version

[nickanderson]

Previously doing something like cfbs update masterfiles@3.24.4 when running 3.24.1 would simply update to the latest version available in the index (while telling you it updated to the version you requested)

cfbs update masterfiles@3.24.4
    [main 8ab9378] Updated module 'masterfiles' from version 3.24.1 to version 3.24.4
     1 file changed, 3 insertions(+), 3 deletions(-)
    Updated module 'masterfiles' from version 3.24.1 to version 3.24.4?
jq -r '.build[] | select(.name=="masterfiles") | {version, commit}' cfbs.json
  {
    "version": "3.27.1",
    "commit": "15d8ca2ca951db3ddf197b90c9dea6ef75f5fa89"
  }

Ticket: ENT-14170

[nickanderson]

First commit failed the test as expected, second commit made it pass.

[nickanderson]

I am unsure that this is exactly desired behavior ^

[craigcomstock]

@olehermanse why does "update" allow a version at all? It would seem to me that the update subcommand might just fail if a version with @version is specified.

If that is the case then I suppose cfbs add would have to be used to change the version of an already installed module?

[craigcomstock]

@olehermanse why does "update" allow a version at all? It would seem to me that the update subcommand might just fail if a version with @version is specified.

If that is the case then I suppose cfbs add would have to be used to change the version of an already installed module?

[craigcomstock]

squash the commits yeah?