Retain original API version in LocalPackageReference

[theunrepentantgeek]

What this PR does / why we need it:

@matthchr noticed that a couple of our configuration errors were giving some odd recommendations (formatted for clarity):

Error during code generation:
failed during pipeline stage 21/63:
Apply export filters to reduce the number of generated types:
group dbformariadb:
version 2018-06-01 not seen (did you mean 20180601?):
version 2018-06-01: type ServersDatabases not seen (did you mean ServersDatabase?):
type ServersDatabases: $exportAs: Database not consumed

On one line it indicates 2018-05-01 was not seen, but then it is quoted it on the very next line.
Also, the suggestion is incorrect as we don't want to elide the hyphens (-)

The root cause is that in LocalPackageReference instances we were removing the hyphens as a part of constructing the package name. Fix is to retain the apiVersion independently of the packge version.

Prerequisites

• Merge Support wildcards with transformation targets #2325

How does this PR make you feel: