Align warning message in console for better readability

[alexander-yevsyukov]

When building Validation with latest dependencies I got the following console output. I'm placing the screenshot with slightly shrinked IDEA app window to hightlight the matter:

The text we are puttin into the console is this:

> Task :java-tests:runtime:launchTestProtoData
w: file:///Users/sanders/Projects/Spine/validation/java-tests/runtime/src/test/proto/spine/test/validation/range_option_test.proto:41:5: Unsigned integer types are not supported in Java. The Protobuf compiler uses signed integers to represent unsigned types in Java (https://protobuf.dev/programming-guides/proto3/#scalar). Operations on unsigned values rely on static utility methods from `java.lang.Integer` and `java.lang.Long` classes (https://www.baeldung.com/java-unsigned-arithmetic#the-unsigned-integer-api). Be cautious when dealing with unsigned values outside of these methods, as Java treats all primitive integers as signed.
w: file:///Users/sanders/Projects/Spine/validation/java-tests/runtime/src/test/proto/spine/test/validation/range_option_test.proto:54:5: Unsigned integer types are not supported in Java. The Protobuf compiler uses signed integers to represent unsigned types in Java (https://protobuf.dev/programming-guides/proto3/#scalar). Operations on unsigned values rely on static utility methods from `java.lang.Integer` and `java.lang.Long` classes (https://www.baeldung.com/java-unsigned-arithmetic#the-unsigned-integer-api). Be cautious when dealing with unsigned values outside of these methods, as Java treats all primitive integers as signed.

It would be better to wrap the text of one warning with proper indentation. It would make these warnings:

1. Easier to read and understand. The user won't have to force his eyeballs travel the whole width of the screen back and forth.
2. Easier to navigate. Indentation would form w: prefixes as bulleted items.

It should look like this:

> Task :java-tests:runtime:launchTestProtoData
w: file:///Users/sanders/Projects/Spine/validation/java-tests/runtime/src/test/proto/spine/test/validation/range_option_test.proto:41:5: Unsigned integer types are not supported in Java.
   The Protobuf compiler uses signed integers to represent unsigned types in Java.
   See: https://protobuf.dev/programming-guides/proto3/#scalar
   Operations on unsigned values rely on static utility methods from `java.lang.Integer` and `java.lang.Long` classes. 
   See: https://www.baeldung.com/java-unsigned-arithmetic#the-unsigned-integer-api
   Be cautious when dealing with unsigned values outside of these methods, as Java treats all primitive integers as signed.
w: file:///Users/sanders/Projects/Spine/validation/java-tests/runtime/src/test/proto/spine/test/validation/range_option_test.proto:54:5: Unsigned integer types are not supported in Java.
   The Protobuf compiler uses signed integers to represent unsigned types in Java.
   See: https://protobuf.dev/programming-guides/proto3/#scalar
   Operations on unsigned values rely on static utility methods from `java.lang.Integer` and `java.lang.Long` classes. 
   See: https://www.baeldung.com/java-unsigned-arithmetic#the-unsigned-integer-api
   Be cautious when dealing with unsigned values outside of these methods, as Java treats all primitive integers as signed.

Notice that I do not wrap the first line which gives the path to the file with line number and error diags. These lines can be automatically picked up by tools analysing the console output. The text which follows is auxiliary, but we need to make it easier to read and jump throught the repetitions.

We probably need to give the auxiliary piece once or twice, and them refer to it as "* Reported in details earier.", as Gradle does for repeated errors.

[alexander-yevsyukov]

As a source of inspiration for resolving this issue, please have a look at how Rust compiler reports the errors.

[alexander-yevsyukov]

As a part of this issue let's change the start of the warning message. Now we have this:

Unsigned integer types are not supported in Java.

The problem with this sentence is that it's too broad. Java can support unsigned integer types, and Guava proved that. Unsigned integer types are just not a part of the JDK and libraries, and the generated code uses "native" Java types.

Let's have this text (full version):

w: file:///Users/sanders/Projects/Spine/core-java/server/src/testFixtures/proto/spine/test/tuple/quintet.proto:53:5: Unsigned integer types declared in Protobuf are backed by **signed** types in the generated Java code.
   See: https://protobuf.dev/programming-guides/proto3/#scalar.
   Validation operations on unsigned values rely on static utility methods `compareUnsigned()` from `java.lang.Integer` and `java.lang.Long` classes.
   Be cautious when dealing with unsigned values outside of these methods.

Changes I've suggest:

• Removing the link to www.baeldung.com article.
• Do not repeating the fact that Java treats integers as signed.

@armiol, FYI.