The new format is:
 - fuzzGenericClass(List)
   -> Arguments[List<List<Integer>[]>]

It is especially useful to see the mutator when debugging or trying
out new mutators with @Solo.

Previously, types like List<List<Integer>[]> failed because the
parameterTypeIfParameterized helper function incorrectly filtered out
generic array types. Removed this filtering since the mutation
framework already handles supported type matching.

When mutating char[] randomly interpret the bytes from libFuzzer as
individual (single byte) chars. This helps to make use of libFuzzers
table of recent compare entries (encoded as CESU8) if the char[] is used
as a String inside the fuzz test.

... otherwise the ArgumentsMutatorFuzzTest can timeout on Windows
runners. A longer execution of this fuzz test is done as part of a
scheduled workflow.

The previous `Class#getName()` uses the JVM type descriptors for arrays,
which leads to non user-friendly messages, such as:
> WithLength does not apply to java.lang.String, only applies to [B, [I, [J, ...

In some projects, network requests can happen after the fuzz test has
started, but before the user had a chance to configure allowed/denied
connections.

Now the user can start Jazzer with the environmental variable
JAZZER_SSRF_PERMISSIVE_UNTIL_CONFIGURED set to a truthy value and all
network requests will be allowed, until the user specifies otherwise
in the fuzz test using BugDetectors.allowNetworkConnections(...)

bazel-contrib/rules_jvm_external#1444 changed
the command line usage of the MavenPublisher class which now requires a
forth boolean argument to configure `publishMavenMetadata`.