HDDS-11719. Remove dependency on server components from ozonefs-common

[adoroszlai]

What changes were proposed in this pull request?

ozonefs-common depends on some server-side components with test scope, but doesn't actually use any of those. It shouldn't need them, since it's a client-side component.

OzoneFsShell requires commons-cli due to the parent class from Hadoop. It gets the dependency accidentally, because ozone fs uses the ozone-tools classpath, which has it:

ozone/hadoop-ozone/dist/src/shell/ozone/ozone

Lines 191 to 194 in dd22dbe

	fs)
	OZONE_CLASSNAME=org.apache.hadoop.fs.ozone.OzoneFsShell
	OZONE_FS_OPTS="${OZONE_FS_OPTS} ${RATIS_OPTS} ${OZONE_MODULE_ACCESS_ARGS}"
	OZONE_RUN_ARTIFACT_NAME="ozone-tools"

Similarly, TestOzoneFsShell gets the dependency transitively via the server-side components. It started failing after removing the test-scoped dependencies:

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.153 s <<< FAILURE! - in org.apache.hadoop.fs.ozone.TestOzoneFsShell
org.apache.hadoop.fs.ozone.TestOzoneFsShell.testOzoneFsShellRegisterDeleteCmd  Time elapsed: 0.132 s  <<< ERROR!
java.lang.NullPointerException: Cannot invoke "org.apache.hadoop.fs.shell.CommandFactory.getNames()" because "factory" is null
	at org.apache.hadoop.fs.ozone.TestOzoneFsShell.testOzoneFsShellRegisterDeleteCmd(TestOzoneFsShell.java:59)

factory is initialized in FsShell.init() <- FsShell.run() <- ToolRunner.run() (which the test calls), but it fails due to classpath issue, and the test suppresses the exception, leaving factory as null.

Test is updated to let it fail with the original problem, if it happens.

Classpath issue is fixed by removing exclusion of commons-cli in client-side dependencies.

https://issues.apache.org/jira/browse/HDDS-11719

How was this patch tested?

CI:
https://github.com/adoroszlai/ozone/actions/runs/11859467136