feat: allow version specification for deno

[sehnryr]

What does this PR do

Add config field for specifying deno version.

Standards checklist

• The PR title is descriptive
• I have read CONTRIBUTING.md
• Optional: I have tested the code myself
• If this PR introduces new user-facing messages they are translated

For new steps

• Optional: Topgrade skips this step where needed
• Optional: The --dry-run option works with this step
• Optional: The --yes option works with this step if it is supported by
  the underlying command

If you developed a feature or a bug fix for someone else and you do not have the
means to test it, please tag this person here.

[SteveLauC]

Add config field for specifying deno version.

What was the previous behavior?

[sehnryr]

Add config field for specifying deno version.

What was the previous behavior?

deno upgrades to "stable" channel by default and overwrites any other version.

[SteveLauC]

and overwrites any other version.

Say I have all the 3 channels installed, deno upgrade will upgrade the "stable" channel to remove all the other installations? Or can I have 3 channels installed? (Rust allows you to do so, I am not sure about the case of Deno)

Stupid question, if I already have "1.45.0" installed, what will deno upgrade 1.45 do?

[SteveLauC]

Just one tiny issue

[sehnryr]

Say I have all the 3 channels installed, deno upgrade will upgrade the "stable" channel to remove all the other installations? Or can I have 3 channels installed? (Rust allows you to do so, I am not sure about the case of Deno)

Stupid question, if I already have "1.45.0" installed, what will deno upgrade 1.45 do?

I don't think you can install multiple versions of Deno 🤔.

deno upgrade 1.45 won't work as it only recognize semver:

error: Invalid version passed (1.45)

Pass a semver, or a full 40 character git commit hash, or a release channel name.

Usage:
Latest
  deno upgrade

Specific version
  deno upgrade 1.45.0
  deno upgrade 1.46.0-rc.1
  deno upgrade 9bc2dd29ad6ba334fd57a20114e367d3c04763d4

Channel
  deno upgrade stable
  deno upgrade rc
  deno upgrade canary

And if we try upgrading to the same version, deno will recognize it and not replace it.

[sehnryr]

I just found out there's an issue with deno's v1 upgrade arguments as they don't match with v2:

• v1: deno upgrade [--version <version>]/[--canary]
• v2: deno upgrade [<version>]/[stable/rc/canary]

[SteveLauC]

Just some trivial comments, the impl looks generally good

[SteveLauC]

Thanks!