add enforcer rule to make sure hbase-spark / scala aren't dependencies of unexpected modules

We should have an enforcer plugin rule that makes sure we don't have scala and/or hbase-spark showing up in new modules. (based on prior discussions about limiting the scope of where those things show up in our classpath, esp given scala's poor history on binary compatibility)