SOLR-17457: Fix support for --max-wait-secs for bin/solr.cmd

[malliaridis]

https://issues.apache.org/jira/browse/SOLR-17457

Description

On Windows the bin/solr.cmd uses the StatusTool with --max-wait-secs, but the flag is not supported in the new notation, only in the old format -maxWaitSecs.

Solution

This PR adds support for the new notation, so that the bin/solr.cmd does not fail anymore when running bin/solr.cmd start.

Note that this change is not applicable to main because maxWaitSecs is already replaced in StatusTool with max-wait-secs.

Tests

I have manually tested the changes on a Windows system, since I am not sure if we have any Windows-specific test bats.

Checklist

Please review the following and check all that apply:

• I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
• I have created a Jira issue and added the issue ID to my pull request title.
• I have given Solr maintainers access to contribute to my PR branch. (optional but recommended, not available for branches on forks living under an organisation)
• I have developed this patch against the main branch.
• I have run ./gradlew check.
• I have added tests for my changes.
• I have added documentation for the Reference Guide

[epugh]

LGTM. I will leave open for a bit to see if anyone else has a comment.

One thing is that we have a mix of using the Option.builder method in getOptions and then declaring actual private objects. I sort of wish we did it one way or the other across all our tools, just so we had consistency.

[epugh]

I just triggered the tests, and once they pass will merge.

[epugh]

Clicked wrong button!

[epugh]

I ran the test that failed locally, and it looks great....