Add API to use custom error handling when Argument parsing fails

See #370 for the basis of these changes

New changes here:

- Arguments can only have an ArgumentParseExceptionHandler attached if they implement ArgumentParseExceptionArgument
- The substitute value from ArgumentParseExceptionHandler doesn't have to be returned directly
- ExceptionInformation can be provided by arguments
- New NMS method to extract translation keys from CommandSyntaxExceptions

I'm not really sure why this build failed (https://github.com/JorelAli/CommandAPI/actions/runs/5707823776/job/15468200688), but it is definitely TriFunctions fault >:)

Also, some tweaks to the annotations on implementations for NMS#registerCustomArgumentType

Remove obsolete unused type parameter T from InitialParseExceptionParser

Change test classes to default package visibility

#476 (comment)

… related classes

#476 (comment)

…med `Internal`ParseExceptionHandlingArgumentType

…ion logic among Arguments that return numbers

…ts` to `dev.jorel.commandapi.arguments.parseexceptions`

…ument

…mentInfo classes

…rgumentType.string()`

…Argument

…t` rather than `number`

Split each Argument in ArgumentPrimitiveTests into their own classes (Boolean, Double, Float, Integer, Long)

…nContextVerifier` so that ArgumentTests classes can test both types of exceptions

…ifier and InitialParseExceptionContextVerifier to handle shared checking logic on InitialParseExceptionContext and ArgumentParseExceptionContext objects

Also some test javadocs tweaks

I couldn't get the maps to clear while tests were running, but I tried this on a real server and it seemed to work. Commands do need to keep reference their arguments for the parsing step, but if a command is unregistered, its arguments will be removed from the `exceptionHandlers` maps automatically.