Refactor DsnRename into DsnUpdate and introduce immutable rename input

[frankgiordano]

Summary

Refactor DsnRename into DsnUpdate to establish a single entry point for dataset update operations and provide a foundation for supporting additional z/OSMF dataset update APIs in the future.

As part of this refactor, the rename API has been redesigned to use an immutable input object instead of overloaded methods with positional parameters.

Changes

• Renamed DsnRename to DsnUpdate.

• Introduced an immutable RenameInputData class to encapsulate rename request parameters.

• Replaced the overloaded rename methods with a single:

  Response rename(RenameInputData inputData)

• Centralized input validation within RenameInputData.

• Removed mutable request state from the implementation.

• Replaced internal varargs helper methods with strongly typed input.

• Updated unit tests, documentation, and examples to reflect the new API.

Benefits

• Provides a scalable design for future dataset update operations.
• Simplifies the public API by exposing a single rename method.
• Eliminates ambiguity caused by positional method parameters.
• Improves type safety through immutable input objects.
• Centralizes validation and reduces duplicate validation logic.
• Improves maintainability by separating request construction from execution logic.

Example

Before

DsnRename rename = new DsnRename(connection);

rename.dataSetName(sourceDataSet, destinationDataSet);

rename.memberName(dataSetName, sourceMember, destinationMember);

After

DsnUpdate update = new DsnUpdate(connection);

update.rename(
    RenameInputData.forDataSet(
        sourceDataSet,
        destinationDataSet));

update.rename(
    RenameInputData.forMember(
        dataSetName,
        sourceMember,
        destinationMember));

This refactor does not change the underlying z/OSMF rename functionality. It modernizes the API and establishes a consistent, extensible design for future dataset update operations.