SOLR-18515: Preserve hyphenated picocli command names in generated CLI docs

[jaykay12]

Description

Preserve hyphenated picocli command names in generated CLI docs

Follow-up of : #5047 via #5047 (comment)

Solution

The CLI docs generator treated every dash in a filename as a command separator, so solr-package-add-key was published as bin/solr package add key. Copying that invocation fails because the registered name is add-key.

cliCommandPath now splits a filename only where the prefix is itself a generated page. Dashes inside the leaf command stay in the name. Page titles, the navigation labels, and the migrated-commands table all use that path.

Regenerated pages for add-key, add-repo, list-available, list-deployed, and list-installed.
bin/solr zk ls and bin/solr snapshot create are unchanged.

Used Cursor for code generation. Regenrated CLI docs are vetted.

Tests

Please describe the tests you've developed or run to confirm this patch implements the feature or solves the problem.

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
• I have added a changelog entry for my change

[jaykay12]

No CL needed for this, can please add no-changelog label for this?

[jaykay12]

self-review ✅
@janhoy please help review this.

[janhoy]

No CL needed for this, can please add no-changelog label for this?

When there is no code changes, only docs / tests, the workflow does not complain about changelog.

Something you can try next time: We now have another way of doing it. Simply add a comment /no-changelog on the PR, and the label will be set.