java: fix kudu-client builds with TSAN-only thirdparty
java: fix kudu-client builds with TSAN-only thirdparty

This turned out to be somewhat messy as only newer versions of maven[1]
allow profile activation when multiple conditions are true.

I tested this via repeated calls to "mvn help:active-profiles" and
"mvn clean compile" while hiding various combinations of my tsan,
uninstrumented, and system protoc executables.

1. https://issues.apache.org/jira/browse/MNG-4565

Change-Id: I580d69507abf0e486fc8f3f364177d0a60b6382b
Reviewed-on: http://gerrit.cloudera.org:8080/4577
Tested-by: Adar Dembo <866ca730bfc7f544e3ebce604ceeba4879f23df0@cloudera.com>
Reviewed-by: Jean-Daniel Cryans <4bf4c125525b8623ac45dfd7774cbf531df19085@apache.org>

cloudera/kudu,andrwng/kudu,InspurUSA/kudu,helifu/kudu,EvilMcJerkface/kudu,InspurUSA/kudu,andrwng/kudu,helifu/kudu,andrwng/kudu,EvilMcJerkface/kudu,InspurUSA/kudu,InspurUSA/kudu,andrwng/kudu,helifu/kudu,helifu/kudu,andrwng/kudu,andrwng/kudu,EvilMcJerkface/kudu,cloudera/kudu,EvilMcJerkface/kudu,andrwng/kudu,helifu/kudu,EvilMcJerkface/kudu,EvilMcJerkface/kudu,EvilMcJerkface/kudu,InspurUSA/kudu,cloudera/kudu,cloudera/kudu,cloudera/kudu,EvilMcJerkface/kudu,EvilMcJerkface/kudu,andrwng/kudu,helifu/kudu,cloudera/kudu,InspurUSA/kudu,cloudera/kudu,cloudera/kudu,InspurUSA/kudu,helifu/kudu,cloudera/kudu,InspurUSA/kudu,andrwng/kudu,helifu/kudu,helifu/kudu,InspurUSA/kudu