add 'Version ' to nameID 5 version string, per MS OT spec

[thundernixon]

Inter's nameID 5 formatting was been improved by 20aaab6, but still fails FontBakery check 055:

🔥FAIL: Version format is correct in 'name' table?

• com.google.fonts/check/055
• 🔥FAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "3.4;6e0206421" [code: bad-version-strings]

According to the Microsoft OpenType spec for nameID 5:

Version string. Should begin with the syntax “Version .” (upper case, lower case, or mixed, with a space between “Version” and the number).

This PR is a small change that makes that happen, allowing Inter to successfully pass check 055.

[rsms]

Yikes. This is pretty messed up I think, that the text "Version " needs to appear in the value for the field "version". Oh well, we live with the mistakes of the people who came before us I suppose :–)

[thundernixon]

pretty messed up that the text "Version " needs to appear in the value for the field "version"

😄 Haha, yeah, it doesn't really make the most sense, but these are the kinds of things that get frozen into things once they're implemented in a bunch of software. Thanks for the merge!