Allow <muleVersion>3.9.2 09-20-2019</muleVersion> for cloudhub deployment

[ca-stefan-cordes]

Currently is limited to carry a major version only:
e.g. <muleVersion>3.9.2</muleVersion> or <muleVersion>4.2.1</muleVersion>.

Due to mule-hotfix workflow the worker gets the newest hotfix runtime in case of

• new deployment
• update mule to newer minorVersion.

This leads to (eventually) get runtimes on production that not have been tested on test-environments (sandbox).

Request is to be able to specify the runtime update during . Either via

• append internal name <muleVersion>3.9.2 09-20-2019</muleVersion> (not nice)
• add new attribute: <muleVersionName>09-20-2019</muleVersionName>
• or/and new attribute: <muleVersionId>5d853858e09d7e2c47529e49</muleVersionId>

and modify your deploy entpoints (PUT https://anypoint.mulesoft.com/cloudhub/api/v2/applications/) accordingly.

Example runtime for values above:
https://anypoint.mulesoft.com/cloudhub/api/mule-versions/3.9.2/updates/5d853858e09d7e2c47529e49

{
	"id": "5d853858e09d7e2c47529e49",
	"name": "09-20-2019",
	"releaseDate": 1569011800524,
	"releaseNotes": "https://docs.mulesoft.com/release-notes/cloudhub-runtimes-release-notes",
	"flags": {
		"performLog4jReplacement": true,
		"skipMMCPairing": true,
		"log4j1Used": false,
		"usingMuleAgent": true,
		"vpnSupported": true,
		"monitoringSupported": true,
		"objectStoreV1": false,
		"loggingNgSupported": true,
		"diagnosticsSupported": true,
		"persistentQueuesSupported": true,
		"asyncScheduleSupported": false,
		"muleLivenessSupported": false
	}
}

See https://help.mulesoft.com/s/ideas#0872T0000009uk9QAA