Problem arguments must be consistent

Several methods in ProblemReporter pass inconsistent problem arguments to handle(..)

• one variant of problem arguments is passed as NoArgument or similar
• the other variant passes a non-empty array

This will blow up whenever the error message (containing placeholders {0} ...) should be rendered using NoArgument: will try to read [0] from the 0-length array => AIOOBE. One case was observed in the context in JSR 199, where each and every such occurrence can throw.