Include / improve code style checks

[AFaust]

FEATURE / ENHANCEMENT

We already have some base conventions in our project documentation and also some tooling in our build process that checks for conventions in our JS files. Still, in the recent PR #81 we encountered various minor issues that may trick people up. We should strive to improve this situation and check the following options:

• including IDE-specific formating configuration in the project(s)
• check current jshint configuration for style consistency between front-end and back-end (I think I may have given front-end some leeway when migrating features from Alfresco Support Tools to avoid being blocked on legacy code issues)
• include Maven validation plugin(s) for Java / JavaScript code style, copyright header presence and generic text file validations (e.g. properly encoded characters in I18n files, use of UTF-8 encoding in source files etc

[binduwavell]

I'm a fan of using http://editorconfig.org/ for common format specification within a project. Most IDEs including IntelliJ and Eclipse have plugins that will configure the IDE to handle the project specific requirements.