Fall back to hard-coded p4ruby version strings.
While a little bit more work, our tools don't really account for filenames with version numbers in them.
Additionally, this avoids having lots of files hanging around just because we've tested p4ruby against updates to dependencies (the p4api). Releases should be *very* rare, and the general rule is just to update the version whenever you make a release to rubygems.