Make `manifest.json` `_version` entry dependent on UI5 version

[petermuessig]

https://github.com/SAP/ui5-manifest/blob/master/mapping.json

[wridgeu]

This seems like the appropriate place to ask if, or in what capacity, manifest changes are going to be reflected in the templates. For now I assume that a complete dynamic creation of the manifest.json, based on its version, is not planned.

Concrete Case
Some colleagues of mine stumbled over this recently. They created a UI5 project with the latest (1.131.1) UI5 version served via the CDN for some local testing. When navigation came into place they stumbled over the following error:

Which was resolved when adjusting the viewPath property to the more current path property, see JSON schema.

Template file in question (reflecting "_version": "1.12.0"):

generator-ui5-app/generators/app/templates/webapp/manifest.json

Lines 58 to 65 in e06705c

	"config": {
	"routerClass": "sap.m.routing.Router",
	"viewType": "XML",
	"viewPath": "<%= appId %>.view",
	"controlId": "app",
	"controlAggregation": "pages",
	"async": true
	},

- I'm not sure if this or something similar was also the intention behind this issue @petermuessig? :)

Note: I do understand that this might most likely be only an issue in the more recent UI5 versions, where this is is actually a "breaking" change/difference in the manifest config.

---

To be fair, I actually was not aware of this change or even the existence of legacyTargetAddition myself. ^^