Enhancing version field...

First, I based on this on the 4.0.x code base because the 4.5 one when built, doesn't work for me with my local Jenkins and 4.5 XL Deploy, so I went with what I think was most stable. This also contains a few other commits of "rejected" mods. If the core of this request, which is described below, would be accepted, if desired, I can properly redo the changes on a 4.5 branch fork to make merging easier.

There seemed to be some better ways to handle the version field(s) in terms of a logical flow. The input field was moved to the Package section since this is when you would definitely be specifying the version in an open "free-flow" kind of method. In the Deployment section, a select drop-down was added that was filled with the current deployment packages for the specified application from the XL Deploy repository. This makes Jenkins jobs that are strictly "Deployment" jobs incredibly easier to configure by guaranteeing the deployment package/version is accurately configured.