IGNITE-29122 Fix javac and javadoc warnings in the build log

[NSAmelchev]

Five public API members documented as deprecated get the missing @Deprecated annotation, so users see the warning the javadoc promises; getTracingSpi() is marked for removal like its setter. A test method and two private constants carried a @deprecated tag by mistake and now have plain comments.

Varargs calls with a bare null or an array of a different type are made explicit. Where the callee treats null and an empty array the same, the argument is dropped; otherwise the cast states the intent. No behavior changes.

Unescaped < and & in javadoc are wrapped in {@code} or escaped in code samples, and two ASCII diagrams are wrapped in <pre>{@code} so the generated HTML stops being broken. The per-module javadoc caps its output at a hundred warnings, so a few sites surfaced only after the first ones were fixed.

The licenses profile no longer logs an Ant exception with a stack trace for the five modules with the pom packaging, where the generated licenses file never exists; a genuine failure of the move now fails the build instead of being swallowed.

[github-actions]

Possible compatibility issues. Please, check rolling upgrade cases

This PR modifies protected classes (with Order annotation).
Changes to these classes can break rolling upgrade compatibility.

Affected files:

• modules/control-utility/src/test/java/org/apache/ignite/util/GridCommandHandlerTest.java