Fix IllegalAccessError analyzing Java compiled with --add-exports (#837)

[jozanek]

Fixes #837.

The crash is ClassToAPI reflectively loading an inner class whose superclass is inaccessible (a module-internal type reached via --add-exports); the IllegalAccessError propagated out and aborted the whole compile.

• ClassToAPI.loadInnerClass now catches IllegalAccessError alongside ClassNotFoundException/NoClassDefFoundError, so an inner class that can't be linked in the analysis classloader is logged and skipped instead of crashing. Structural errors (VerifyError/ClassFormatError/…) are intentionally left to propagate as genuine classfile problems.
• JavaAnalyze no longer silently drops a class that fails reflective loading: it records the product, member-ref dependencies, and direct inheritance dependencies (superclass + interfaces) for it, derived from the classfile. Canonical names are reconstructed from the InnerClasses attribute.
• module-info.class is explicitly excluded from that fallback (it is deliberately not analyzed as a class).

Known limitation / follow-up

The un-loadable class still gets no api.ClassLike recorded (API extraction is reflection-based and the class can't be loaded), so name-hashing can miss dependents when that class's own public shape changes. Pre-existing and shared with the NoClassDefFoundError case (sbt/sbt#117). The complete fix — classfile-based Java API extraction — would also resolve #151 and #1697 and is best done separately.

[jozanek]

Follow up PR: jozanek#1

[jozanek]

And here's phase 3: jozanek#2

P.S. I already signed CLA, feel free to rerun the last failing step in workflow.

[eed3si9n]

Thanks!