Correct but failing test for lenient parsing of bad version number
Change output range for PackageVersionParser.versionMagnitude

It's now back to returning 10000 for "1.0.0", as it was before
the recent changes to allow for wrapped package version numbers
and prerelease versions. Given that there are other constants
in the cost function used in the constraint solver, this gives
us much more confidence that we haven't fundamentally changed
the behavior of `meteor add` or `meteor update` in 0.9.3.
Uncomment test for `meteor search` with malformed versions
Ignore packages with malformed versions or malformed constraints

This allows us to later increase the pool for well-formed versions without requiring
moving the catalog's data.json into a new folder, which would require re-syncing
the entire catalog.
Merge branch 'release-0.9.3-lenient-version-numbers' into release-0.9.3

Conflicts:
	tools/package-version-parser.js