Rearrange order of exchange type and host as well as making their fields width the same

[Andrey9kin]

Definition of Done for the pull request

• [ ] Travis CI build is passing (includes unit tests and static analysis)
• [ ] You submission reviewed by one of the maintainers
• [ ] New functionality covered by unit tests
• [ ] Help messages for UI updated
• [ ] Screenshots in README.md updated
• [ ] JobDSL help updated
• [ ] Groovy script for global configuration updated

  Recomendations

  Pull request title

• Fix #X: <issue X title> in case if you have an issue
• Update for the change introduced in #X (where X is issue or pull request) in case of no issue

  Merging pull request

Please use squash merge by default unless you have a very good reason not to do so

[Andrey9kin]

@MadsNielsen I changed exchange type drop down the list to doFill. However, I agree with @alexsedova that it is clearer when you list options in the jelly file itself. The reason for the change is that jelly renders different fields width for those two types which look ugly. So have to align

[MadsNielsen]

@Andrey9kin Taht's alright, i was just curious as to why we were using Jelly. If you do it in jelly you've got more maintainence because you have to make sure your string values, matches your enums in code...for instance. For me it's just easier to use the ListBoxModel for those sorts of things.

Btw...i like the direction with all those options you're adding to the RabbitMQ trigger.

[alexsedova]

@MadsNielsen I tried to use ListBoxModel in doFillJenkinsMagicFunction but I fault to save exchangeType. We needed the fix asap and I went the fastest way to add static options to jelly form.