Better error reporting in dev

[shartte]

• This makes use of the changes in Refactor ModLoadingIssue Warning/Error Translations #167 to be able to freely convert a translation between error/warning
• It now reports the full set of incompatibility issues as errors when in dev, instead of falling back to a generic "brokenfile" error as before
• Added tests for more cases
• Made it so that an unknown FMLModType is now reported as a normal incompatibility, using the following adjustment:
  • If a ModFileReader throws a ModLoadingException, the contained issues are recorded as incompatibilities and will be reported, if no other reader successfully reads the file. The reporting level will be inherited (warning in prod, error in dev)
  • Any other exception continues to be reported as a loading error

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

Last commit published: c73b537f51b6d59936321f8d2e335318264f01bb.

PR Publishing

The artifacts published by this PR:

• 📦 net.neoforged.fancymodloader:earlydisplay:4.0.14-pr-170-better-dev-errors
• 📦 net.neoforged.fancymodloader:loader:4.0.14-pr-170-better-dev-errors
• 📦 net.neoforged.fancymodloader:junit-fml:4.0.14-pr-170-better-dev-errors

Repository Declaration

In order to use the artifacts published by the PR, add the following repository to your buildscript:

repositories {
    maven {
        name 'Maven for PR #170' // https://github.com/neoforged/FancyModLoader/pull/170
        url 'https://prmaven.neoforged.net/FancyModLoader/pr170'
        content {
            includeModule('net.neoforged.fancymodloader', 'earlydisplay')
            includeModule('net.neoforged.fancymodloader', 'loader')
            includeModule('net.neoforged.fancymodloader', 'junit-fml')
        }
    }
}