Beachball updating package.json version for private package

[Vidit Mathur]

Currently beachball collects package info at the start of publish process and it might use a pre-fetched remote repo version, and post publish it performs the package bump, till this point it can happen that a manual update to package.json has been pushed for a private package.

Now this update is actually ignored, and the info collected earlier is used to update the package.json version during the bump process and even for private package this step is not skipped.

Ideally for private package package.json version update should not happen.