Allow User to Change Version Number of Component

[jmwright]

A user should not need to edit the package.json file to update the version number of their component. The version numbering scheme is as follows, and will need to be documented somewhere like the main Sliderule repository.

X.Y.Z
X = Major version number - the behavior and/or characteristics of the hardware (electrical, mechanical, etc) has been changed.
Y = Revision - a change was made to the design source that does not effect how the hardware works, but is a change all the same.
Z = Errata - Documentation changes, or other changes that don't alter the source of the design. For example, if a typo is fixed in a readme file.

All non-COTS (Commercial Off-The-Shelf) components should start at version number v1.0.0, no matter what release state it's in. There is no concept of a Mk 0 release. COTS components should have a version number v0.0.0 so that they can be filtered out in certain cases.

The command for this could take the form of sr version change .level1.level2 v1.1.0.