Teach the ByteCodeAnalyzer to extract annotations from .class files

The result is a map suitable for use by the annotation indexer.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Use the ByteCodeAnalyzer to write the annotation index

Instead of loading the classes, we read the annotations directly from the
.class files. This has two advantages over the previous method:

1. We avoid polluting the ClassLoader with loaded classes (which can be
   problematic e.g. when ij1-patcher wants to patch the classes before
   loading them at a later stage).

2. It is no longer necessary for the dependencies of the classes to be
   on the class path (though that is only true for the classes, not for
   the annotations).

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Remove unused code from ByteCodeAnalyzer

These lines were identified by Eclipse as unneeded.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Streamline the ByteCodeAnalyzer

As far as the annotation indexer is concerned, we need not parse
interfaces, fields nor methods. So let's skip that part and cut to the
chase.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>