ECJ batch compiler logs INFO different then WARNING

from https://ci.eclipse.org/jdt/job/eclipse.jdt.ui-github/job/PR-997/1/consoleFull
```
23:22:02 [INFO] --- tycho-compiler:4.0.5-SNAPSHOT:compile (default-compile) @ org.eclipse.jdt.ui ---
23:22:02 [INFO] Compiling 1783 source files to /home/jenkins/agent/workspace/eclipse.jdt.ui-github_PR-997/org.eclipse.jdt.ui/target/classes using Eclipse Compiler for Java(TM) 3.36.0.v20231114-0937
23:22:23 [WARNING] /home/jenkins/agent/workspace/eclipse.jdt.ui-github_PR-997/org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/SuppressWarningsSubProcessor.java:[65]
23:22:23 static final String ADD_SUPPRESSWARNINGS_ID= SuppressWarningsSubProcessorCore.ADD_SUPPRESSWARNINGS_ID;
23:22:23 ^^^^^^^^^^^^^^^^^^^^^^^
23:22:23 The field SuppressWarningsSubProcessor.ADD_SUPPRESSWARNINGS_ID is hiding a field from type SuppressWarningsSubProcessorCore
23:22:23 3. INFO in /home/jenkins/agent/workspace/eclipse.jdt.ui-github_PR-997/org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/java/correction/ChangeCorrectionProposal.java (at line 195)
23:22:23 ITextOperationTarget textOperationTarget= activeEditor.getAdapter(ITextOperationTarget.class);
23:22:23 ^^^^^^^^^^^^
23:22:23 Potential null pointer access: The variable activeEditor may be null at this location
23:22:23 [WARNING] /home/jenkins/agent/workspace/eclipse.jdt.ui-github_PR-997/org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/actions/RefactoringActions.java:[53]
23:22:23 private static IType convertToEnclosingOrPrimaryType(IJavaElement element) throws JavaModelException {
23:22:23 ^^^^^^^^^^^^^^^^^^
23:22:23 The declared exception JavaModelException is not actually thrown by the method convertToEnclosingOrPrimaryType(IJavaElement) from type RefactoringActions
```

As a consequence jenkins seems to be confused


Also note, that problem number 1 or 2 was not logged at all, somehow the INFO got number 3 after only 1 warning

source was added with https://bugs.eclipse.org/bugs/show_bug.cgi?id=496137 [compiler][batch] support INFO problem severity

Start with the ECJ batch compiler logging behavior shown in the report, then review the related source history from Bug 496137, which introduced INFO problem severity. Trace how INFO and WARNING problems are numbered and formatted. Done means the compiler reports each problem with consistent severity labels and sequential numbering without confusing Jenkins.

Written by the indexing model from the issue text.