Tests sometimes fail with AppLogWrapper conflicts

Expected behavior

Tests should not fail (or if they have errors unrelated with AppLogWrapper, those errors should be reported instead).

Actual behavior

Occasionally, the tests will fail to build with the following error:

Cannot access class 'org.wordpress.android.fluxc.utils.AppLogWrapper'. Check your module classpath for missing or conflicting dependencies

Steps to reproduce the behavior

It is not clear if this will reliably reproduce the issue, but it has been observed following these steps:

1. Introduce a compile error in a test file
2. Try to build / run the test implementation
3. 💥 The above error is reported instead

Note: in case this occurs, even after fixing the underlying error, the above error will still be reported until a clean / build is performed.

Until this is properly resolved, the work-around for now is to clean and rebuilt after resolving the other errors.

To properly fix this, it is probably best to resolve the circular dependencies between WordPress-Android and WordPress-FluxC-Android (specifically in the test implementation, and regarding our usages of AppLog and AppLogWrapper classes).

Start by examining the WordPress-Android and WordPress-FluxC-Android test implementation and their usages of AppLog and AppLogWrapper. Reproduce the failure by introducing a test compile error, then clean and rebuild; done means the underlying test error is reported without the AppLogWrapper classpath conflict.