Build scripts: run checks only when commit changes files with certain type

[php-coder]

Most of our checks are checking only files with a certain type. We'll have a benefit if we run them only when user modified files with certain types.

Examples:

• sortpom checks only pom.xml
• bootlint checks only *.html files
• html5validator checks only *.html files
• jasmine needs to be run only when we changed *.js
• license plugin checks only *.java and *.groovy files
• probably we need to run enforcer only when pom.xml has changed
• codenarc should run only for *.groovy files
• checkstyle/pmd should be run only for *.java (and maybe *.properties) files
• we need to check Ansible playbooks only when they were modified (#422)

[php-coder]

If only tests on Groovy were modified then only unit tests and CodeNarc checking should be performed.

[php-coder]

• the checks that are performed by the maven plugins also should be run when pom.xml has been modified to catch the changes in the plugin version/configuration
• the checks that are performed by the maven plugins and that use external configuration also should be run when configuration files have been modified to catch the changes in the plugin configuration
• the tools that are installed manually from .travis.yml also should be run when .travis.yml has been changed to catch the possible changes in their versions/configuration

[php-coder]

I'm going to merge my implementation. Here are some details:

• unit and integration tests run always, regardless what files were modified. There are too many possible factors that can affect application behavior and and I decided to solve only the trivial cases for a now.
• there is no way to disable skipping logic and if you need to run specific check there is no way to force that. I was thinking about introducing environment variable or using a special magic comment from the commit message but decided to leave it as-is for a now (although it can be added later).

[php-coder]

unit and integration tests run always

Actually, we can run unit tests only when one of these were modified: pom.xml, java or groovy files.

Anyway, unit test will be run again during publishing code coverage (see #391).