Junit being pulled in as transitive dependency in compile scope

[SalesforceBrian]

log4j-1.2-api and log4j-api are pulling JUnit in as a transitive dependency in the compile scope. This causes a problem for me as the version of JUnit pulled in has security & license issues that prevent it being deployed in my env.

Since JUnit shouldn't be in the compile scope anyway, and this SDK already explicitly pulls JUnit in to the testscope, we should exclude JUnit from the log4j-1.2-api and log4j-api dependencies