Version command fails when literal version contains leading zeros

Expected Behavior

lerna version 1.1.0124

Should set the version to 1.1.124 (or even 1.1.0124 since NPM doesn't seem to care).

Current Behavior

Fails with "ERR! lerna bump must be an explicit version string or one of: 'major', 'minor', 'patch', 'premajor', 'preminor', 'prepatch', or 'prerelease'."

Possible Solution

Normalize the version number.

My current solution in our CI bash script is this:

# Remove leading zeros in version number parts (Lerna doesn't like them).
shopt -s extglob # Turn on extended globs for the following pattern matching
VERSION=${VERSION##+(0)} # Remove all leading zeros
VERSION=${VERSION/#./0.} # Add a leading zero if only a leading dot (.) remains
VERSION=${VERSION//.+(0)/.} # Remove leading zeros from minor and patch numbers

Steps to Reproduce (for bugs)

{
  "version": "0.0.0",
  "npmClient": "yarn",
  "useWorkspaces": true
}

<!-- If you have a `lerna-debug.log` available, please paste it here -->
<!-- Otherwise, feel free to delete this <details> block -->

Context

Our CI pipeline isn't very strict about putting together version numbers. The patch version frequently has leading zeros. This is the only tool that complains about that.

Your Environment

Start with the lerna version command and the version argument handling; the issue demonstrates the failing input 1.1.0124 and includes a sample lerna.json. Verify the command accepts the literal version and produces the expected normalized version without the explicit-version error.