CASSANDRA-20876: Offline nodetool commands should not print network options in help

[arvindKandpal-ksolves]

Summary

Offline nodetool commands (e.g. history) do not require a JMX connection,
yet their --help output was showing network-related options like --host,
--port, --password, etc. This is misleading and unnecessary.

Changes

• AbstractCommand.java: Added a public isOfflineCommand() method that
  safely wraps the existing protected shouldConnect() to expose whether a
  command requires a JMX connection.
• CassandraCliHelpLayout.java: Updated parentCommandOptionsWithJmxOptions()
  to suppress JmxConnect options from help output when the command is offline.
  NodetoolCommand options are still always shown for backwards compatibility.
• test/resources/nodetool/help/history: Updated help snapshot to reflect
  the corrected output — JMX network options are no longer shown for history.

patch by Arvind Kandpal; reviewed by TBD for CASSANDRA-20876

[arvindKandpal-ksolves]

Thanks for the feedback @Mmuzaf!

You're completely right about the potential side effects of calling shouldConnect(). I've updated the PR based on your suggestion: I reverted the previous approach, introduced a LocalCommand marker interface, made the History command implement it, and updated CassandraCliHelpLayout to just check instanceof LocalCommand statically.

Let me know if this looks good!

[Mmuzaf]

@arvindKandpal-ksolves , please also add a test to ensure that none of the commands which implement LocalCommand establish a connection. Otherwise looks good!

[arvindKandpal-ksolves]

Thanks for the feedback @Mmuzaf!

Added the test testLocalCommandsShouldNotConnect in NodetoolClassHierarchyTest
to ensure all LocalCommand implementations do not establish a JMX connection.
Also restored the shouldConnect() override in History as it was needed for the test to pass.

Both HistoryTest and NodetoolClassHierarchyTest pass successfully.