Enables admins to express file naming patterns for which lines of code should not be counted

This is a fork that may not ever be merged into the main project. It enables Sonarqube admins to suppress "lines of code" counting for specific files.

Specific examples of how this functionality can be useful:

• Your builds generate an "effective-pom.xml" build file and you have rules to flag problems found there.
• Your builds generate a report of all classloader collisions and you have rules to flag any where the classes that collided aren't identical.

In scenarios like these your lines of code count might be 5000 on a project with 300 lines of Java code, 300 lines of XML Spring configuration, 300 lines of pom.xml file, and 4100 lines of effective-pom.xml & other build-generated reports such as the classloader collision report. You can't simply exclude these files from Sonarqube's view altogether because you want rules to run against them and issues to be raised.