Go1.11 + fix helloweb + change helloweb-go to be done via gowork
While helping @romain to review my current work we tried to build helloworld and found that it is completely broken.
It was first minimally fixed to pin eggs and the like, but helloweb-ruby was not completely fixed. Nevertheless I decided that it is better we have at least go/python fixed instead of whole helloworld being completely bitrotted (it would be good for lab-related folks to look into helloweb-ruby breakage as the same infrastructure is used in software/gitlab/).
Then I've added Go1.11 to our stack, so that recent-enough compiler/stdlib could be used. A note goes here that currently our lab uses go1.9 which is outdated and not supported by upstream, and other bits are still using go1.10.3 while go1.10.7 was already released some time ago with bug and security fixes. I did not touched neither go1.10 / nor go1.9, but imho it makes sense for infrastructure people to look into appropriate upgrades.
Finally component/helloweb/ is switched to use gowork infrastructure (see 1b540151 for gowork introduction). Today gowork is used to build eveything go-related, so building go bits manually via cmmi as example is a bit misleading. Gowork is also required in case we'll need to use any third-party or our package a helloweb-go.
/cc @jerome, @luke, @alain.takoudjou, @tomo