Support correcting of App Highest Version in deployment

While building a deployment package Mendix defaults the app package version to the highest app or brach tag.

However, when a developer makes an error in the versioning, this default value keeps jumping to the faulty high version.

This doesn't look nice, and with the new Pipeline tool, the pipeline uses this tag automaticly and doesn't allow for overrides.

This is an example, a junior dev did not understand the deployment quite yet. Our actual version is 3.19.0.

Either allow developers to alter this highest tag value or allow a ticket to fix it on the Mendix side (currently the feedback is, pitch it on the ideas forum, so here I am).