add stage 2 compatibility for FabricLoader subclasses e.g. lunar client

[Traben-0]

I am unable to test via local maven due to build failures on windows due to it generating directories with ":"

If there is some other testing method @Johni0702 i'd like to learn it / give it a go before we merge, also just to make sure there isnt anything else affecting this linear issue that the reporter may have missed.

Linear: EM-3472

[github-actions]

Test Results

16 files  ±0  16 suites  ±0   11m 41s ⏱️ -4s
95 tests ±0  95 ✅ ±0  0 💤 ±0  0 ❌ ±0 
99 runs  ±0  99 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 4e584e7. ± Comparison against base commit d75286a.

♻️ This comment has been updated with latest results.

[Johni0702]

suggestion: Instead of simply dropping these, we could accumulate them and then attach them as the cause to the final exception we throw. That way it'll hopefully be clearer which classes it tried and why it rejected each one.

Exception ex;
while (...) {
   try {
        ...
   } catch (NoSuchFieldException e) {
        if (ex == null) ex = e;
        else ex.addSuppressed(e);
        ...
   }
}
throw new ClassNotFoundException("Could not find the FabricLoader implementation class", ex);

[Traben-0]

testing confirms it solves this issue on launch via lunar client