Build automation using Yetus pre-releases shouldn't assume test-patch runs directly from a src checkout

HBASE-23873 reports that several places where CI tools allow for running with a Yetus that is not a release build are broken. The gist from that ticket is that at some point, Yetus restructured its precommit/src module and now paths are broken. In a discussion, Sean Busbey mentioned that we should not assume that test-patch can be run directly from a source checkout and probably the automation should instead depend on (or perform) a build of the specified Yetus sources before consuming them. Thus this ticket documents the issue.