GUI: changes to make GWT SuperDevMode working

 - Since all majo browsers dropped support for bindings necessary
   to compile GWT plugin, we can no longer use DevMode.
 - Modified GWT modules definitions to support SuperDevMode.
 - Since static files in webapp folder are not deployed to web root when starting
   SuperDevMode, we must put same files in public package referenced from
   modules gwt.xml in /resources/.../webgui/public/. This solution
   is not nice, but it's working. Would be simpler, if we could define
   something like "level-up-folder" in package name.
GUI: more coherent version for SuperDevMode

- Specify module names to build in pom.xml profiles
- Prevent passing /webapp content to result war, it's now done
  by gwt compiler instead.
- Added modules Dev and SuperDev (first is standard devel compile
  with less browsers, second enables super dev mode for
  compiled app - used only locally).
- Web files structures changed, .html, .css and any other files
  are now in src/resources/common/.../webgui/web and they are put
  in resulting war inside module folders and not parent folder.
  This provide such resources to apps runned in both compiled and
  superDev mode.

- There is only one minor bad thing, that common resources files
  (content of /js and /img folders) are copied to each module, so
  they are contained 3 times in resulting web app.
  Letting war plugin handle this doesn't help, since we wouldn't
  have such resources available in super dev mode (we can't, at
  least for now, diferentiate their location in super dev mode).