Randomize short/long opts usage in Java-based CLI tests

We have a decent suite of Java tests that validate "bin/solr" usage, including (but not limited to):

• AuthToolTest
• CreateToolTest
• DeleteToolTest
• PackageToolTest
• HealthcheckToolTest
• SolrCLIZkToolsTest

Each of these tests triggers a tool with a (mostly hardcoded) set of string-literal parameters, e.g.

    String[] args = {
      "auth",
      "enable",
      "-z",
      cluster.getZkClient().getZkServerAddress(),
      "--auth-conf-dir",
      dir.toAbsolutePath().toString(),
      "--solr-include-file",
      solrIncludeFile.toAbsolutePath().toString(),
      "-credentials",
      "solr:solr",
      "--block-unknown",
      "true"
    };
    assertEquals(0, runTool(args));

Randomizing the parameter names in these invocations would give us better coverage, and increase our confidence when making changes to the CLI syntax (like that done in SOLR-16824)