Fix VertxConfigmapBooster test

[rohanKanojia]

A recent change in vertx-configmap-booster project has caused the build
process to automatically create resources during build(see src/main/fabric8
in that project). So it's better to edit configmap after build process.
For more details, see openshift-vertx-examples/vertx-configmap-example@2afa3e1

[hrishin]

@rohanKanojia this looks good to me. At the same, this is alarming as well. Its better to move these regression tests close to booster projects.
WDYT?

[rohanKanojia]

@hrishin : Hmm, agreed. I also feel that these booster regression tests should be coupled with those booster projects rather than fabric8 maven plugin.
Roland was also asking about moving these tests out of Fabric8 maven plugin, so maybe we can add them to a repo on that Github org, or maybe add them individually? But that would require configuring CI on each project.

[hrishin]

@rohanKanojia agreed

[rohanKanojia]

@hrishin : Thanks :) . Could we merge this small fix for now? I have created a separate issue for it. Let's move our discussion here

[rohanKanojia]

@piyush1594 : Can you merge this, please?

[piyush-garg]

Thanks @rohanKanojia

LGTM, it is required as all the Travis builds for PR are getting failed, I am merging this. @hrishin