Top level config option to log commandlines for eclipse to parse...

NOTE!  This rely on an updated cpptasks-parallel I’ve already sent a push request for.

This is for eclipse-CDT users who want the logs that CDT expects from a build.
The config-option is at top level and will result in command-line logging at level INFO instead of DEBUG.

The default is of (false) and this feature is activated with <commandLog>true</commandLog> at nar-maven-plugin
top-level config.

Implementation notes.  
AbstrackCompilerMojo now has option boolean commandLog=false. The implementation in NarCompileMojo simply pass this over to modified CCTask. Later, in CUtil.runCommand() the CCTask object is available and the log-level for the one log-call is adjusted depending on query task.getCommandLog() from VERBOSE to INFO...

Did some cleanup of odd logging in NarLogger so that INFO means INFO by default...(O=O)

My usage:
```xml
<project>
  ...
    <profile>
      <id>inEclipse</id>
      <activation>
        <property>
        	<name>buildenv</name>
        	<value>eclipse</value>
        </property>
      </activation>
      <properties>
        <build.commandLog>true</build.commandLog>
      </properties>
    </profile>
  ...
 <build>
  <plugins>
        <plugin>
        <groupId>com.github.maven-nar</groupId>
        <artifactId>nar-maven-plugin</artifactId>
         ...
        <configuration>
             ...
          <commandLog>${build.commandLog}</commandLog>
            ...
        </configuration>
      </plugin>
  </plugins>
</build>
```