Cleanup build tooling and avoid in-repo binaries under test

[lefou]

There are some binaries checked-in which can easily get out of date resulting in potential misleading test results. Those may result in regressions like #285.

@kriegaex posted in #289 (comment)

I am aware of that. I am simply in a tight spot concerning the time at my disposal. The actual problem is that this stuff was ever checked into the SCM in the first place. I eliminated lots of these relics already since I joined the project. These are a bit difficult, because the tests run before the main AspectJ build artifacts (runtime, matcher, weaver, tools) are being built, i.e. we have a circular dependency there. In the future, I will rather spend time fixing the root cause than automating the workaround.