codebase improvements

Nobody has claimed this yet.

The wart remover (http://www.wartremover.org/) and scalastyle (http://www.scalastyle.org/) show a number of places where the codebase could be improved.

Some of the wart remover rules are stupid, like not allowing default method parameters - which is one of the best features of Scala, but it is what it is.

This issue tracks the changes that are needed to bring the codebase into compliance with a subset of the wart remover and scalastyle checks.

To work on this issue, in the CIMSpark pom.xml, add the wartremover compiler plugin to the net.alchim31.maven:scala-maven-plugin within the configuration, add wartremover options to the scala compiler args and comment out the fatal warnings flag:
```

net.alchim31.maven
scala-maven-plugin
${version.dependency.scala-maven-plugin}

${version.dependency.scala}
${version.dependency.scalalibrary}

false



org.wartremover
wartremover_${version.dependency.scalalibrary}
${version.dependency.wartremover}


true

-deprecation
-feature
-unchecked
-Ywarn-dead-code
-Ywarn-unused

-Xlint:_
-target:jvm-1.8


-P:wartremover:only-warn-traverser:org.wartremover.warts.AsInstanceOf

-P:wartremover:only-warn-traverser:org.wartremover.warts.EitherProjectionPartial
-P:wartremover:only-warn-traverser:org.wartremover.warts.IsInstanceOf
-P:wartremover:only-warn-traverser:org.wartremover.warts.NonUnitStatements
-P:wartremover:only-warn-traverser:org.wartremover.warts.Null
-P:wartremover:only-warn-traverser:org.wartremover.warts.OptionPartial
-P:wartremover:only-warn-traverser:org.wartremover.warts.Product
-P:wartremover:only-warn-traverser:org.wartremover.warts.Return
-P:wartremover:only-warn-traverser:org.wartremover.warts.Serializable
-P:wartremover:only-warn-traverser:org.wartremover.warts.StringPlusAny
-P:wartremover:only-warn-traverser:org.wartremover.warts.Throw
-P:wartremover:only-warn-traverser:org.wartremover.warts.TraversableOps
-P:wartremover:only-warn-traverser:org.wartremover.warts.TryPartial


...
```
Recompile some module and then work on resolving the WARNINGs.

Start in the CIMSpark pom.xml by reviewing the scala-maven-plugin configuration and the listed Wart Remover compiler arguments. Recompile a module to surface warnings, then inspect the affected Scala code and work through the warnings from the enabled checks. Done means the selected Wart Remover and Scalastyle checks are enabled and the resulting warnings have been resolved.

Written by the indexing model from the issue text.