GUI: proper support for SuperDevMode

- We can now use super dev mode for GUI development, so it's possible
  to use new firefox (>28) and chrome.
- Only "dev" version (default maven profile) is switched to super dev mode.
- Moved re-captcha script loading from gwt.xml to html since it
  clashed with super dev mode script processing. Also moved in
  production version to prevent double loading.

To run GUI in super dev mode, you must:

1. start codeserver (super dev mode option in intelliJ)
2. visit codeserver URL and copy bookmarks for dev mode on/off (just once)
3. start regular web server (standard dev mode in intelliJ)
4. visit regular web serve URL WITHOUT codeserver definition
5. click on bookmark "dev mode on"
6. recompile module by button in displayed webpage
7. ignore warning that it needs recompile and finally see running webapp

To see changes in code use bookmarks to recompile the module.
To see changes in html/css rebuild regular web server build.
GUI: fixed script loading for super-dev-mode

- Use loading of external scripts in onModuleLoad().
- Removed including in html.
Add new methods for get data with Vos

- add method getDataWithVos (new structure with Vos before Resources)
- add method getRequiredAttributes for service and vos
- add these methods to RPC
- fix privilageException message in ServiceManagerEntry, method
  getDataWithGroups
Merge pull request #356 from stavamichal/getDataWithVoAttributes

Add new methods for get data with Vos
Added authz right for engine

Role.ENGINE can call ServicesManagerEntry.getAssignedServices(sess, facility)
REGISTRAR: fixed behavior for group applications with auto-approve

- Do not throw exceptions when user submits application for group
  with auto-approve and is not member of VO yet. Do not send
  notification to VO admin either.
- When user's application for VO is approved, check for his group
  applications in same VO with auto-approve and try to approve them.
  Get applications based on user and all his identities.

- Trigger member's validation only once - after all applications
  are processed.
REGISTRAR: fixed behavior for group applications with auto-approve

- Do not throw exception when approving of group application fails
  to allow VO application to be successfully approved.
- Fixed javadoc.
- Skip approving NEW applications, since they will be approved once
  user verify his email address.
- Fixed SQL.
Fix security issue with propagation to DNS alias

Facility manager can create destination to any free hostname (or IP
adress). The "free" means that name is not used on other facilty as a
destination or host's name. Exception from this is when the manager is
also facility manager on such facility.
Therefore any facility manger could create destination to any machine
(using IP address on other alias) and create resources with any services
(like sshkeys_root or k5login_root) and Perun will propagate there the
configuration.

Perun-slave now contains two variables DNS_ALIAS_WHITELIST and
FACILITY_WHITELIST which contains from which destinations or
which facilities the perun-slave accepts new configuration.
By default slave only accepts configuration from `hostname -f`.
Add log_debug function to perun slave script

If $DEBUG env. variable is set then this function logs to syslog.
Otherwise it does nothing.
REGISTRAR: optimization

- Save up 1 DB query when auto-approving application.
Merge pull request #358 from zlamalp/registrar

REGISTRAR: fixed behavior for group applications with auto-approve

- Do not try to (auto-)approve applications for group when user is not member of VO.
- When VO admin approves VO application, then try to approve all user's group
  applications with auto-approve mode (search by user-ext-source too, to get
  all applications of user which was submited before user creation). Skip NEW
  applications, they will be approved once user verify his email.
Merge pull request #353 from zlamalp/sdev

GUI: support for super-dev-mode in GWT

- Super-dev-mode is necessary for GUI development in latest version of Firefox (>28) and Chrome.
- Use cross-site linker necessary for super-dev-mode.

- Only devel version of GUI is set to use super-dev-mode, it's not necessary
  for production builds and doesn't affect them.

- Third-party scripts (like Re-Captcha), which needs to be loaded before GUI must
  use ScriptInjector in onModuleLoad() since they can't be part of gwt.xml now. This
  solution works in both versions.

Super-dev-mode benefits for now:

- no need for devel browser plugin
- faster recompile in dev mode (depends on app itself)
- source-maps which points JS exceptions to places in your java code

To run GUI in super-dev-mode, you must:

1. start codeserver (super dev mode build option in intelliJ)
2. visit codeserver URL and copy bookmarks for dev mode on/off (just once)
3. start regular web server (standard dev mode option in intelliJ)
4. visit regular web server url WITHOUT codeserver definition
5. click on bookmark "dev mode on"
6. recompile module by button in displayed webpage
7. ignore warning that it needs recompile and finally see running webapp

To see changes in code use bookmarks to recompile the module.
To see changes in html/css rebuild regular web server build.