dvm use Command Fails Without 'v' Prefix (Unlike dvm install)

[FelixIsaac]

Describe the bug

The dvm use command requires the 'v' prefix for version numbers, while the dvm install command does not, leading to inconsistent behavior and user confusion. The documentation implies that the 'v' prefix is optional for both commands.

To Reproduce

1. Install a specific Deno version using dvm install 2.2.1 (without the 'v' prefix).
2. Attempt to switch to the installed version using dvm use 2.2.1 (without the 'v' prefix).
3. Observe the "version not found" error.

Expected behavior

The dvm use command should recognize and switch to the specified Deno version regardless of whether the 'v' prefix is included, mirroring the behavior of the dvm install command. The 'v' prefix should be optional for both commands (and other related commands) to ensure consistency and ease of use.

Screenshots

Redacted username and computer username for security reasons

Desktop (please complete the following information):

• OS: Windows 11
• Architecture: x86_64
• Version: v0.9.1

Additional context

Note that I'm using Git Bash for my terminal screenshots. Just to add on I believe this inconsistency creates a confusing developer experience, as developers might expect the version number format to be consistent across all DVM commands. Standardizing the version number format (making the 'v' prefix optional) would improve usability.