HDDS-14922. Define invokeRatisServer or invokeRatisClient methods

[Russole]

What changes were proposed in this pull request?

• Add invokeRatisServer(..) to ScmInvoker to centralize Ratis server invocation logic
• Move Ratis server invocation from SCMHAInvocationHandler to ScmInvoker
• Update SCMHAInvocationHandler to delegate DIRECT invocation to ScmInvoker
• Add fallback to the original implementation when ScmInvoker is not available (for backward compatibility)
• Implement the new invocation path for DeletedBlockLogStateManager

Follow-up

• Complete the refactoring for DeletedBlockLogStateManager first; other SCM handlers will be updated in follow-up patches
• Apply the same invocation pattern to invokeRatisClient(..) in future patches

What is the link to the Apache JIRA

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

How was this patch tested?

• All CI checks passed
  • https://github.com/Russole/ozone/actions/runs/23797561288

[Russole]

Hi @szetszwo, could you please review this PR when you have time? Thank you!

[szetszwo]

@Russole , thanks for working on this! We should not use Proxy.newProxyInstance(..) anymore; see https://issues.apache.org/jira/secure/attachment/13081517/10013_review.patch

[szetszwo]

This change does not help since it is after the proxy. We should do it before the proxy.

[Russole]

Thanks @szetszwo for the review. Updated the implementation to handle overloaded @Replicate methods and pass parameter types to invokeRatisServer, ensuring correct method resolution during Ratis invocation.
Without this, incorrect overload resolution could lead to null protobuf arguments being serialized, causing a NullPointerException in CI tests (e.g. TestScmDataDistributionFinalization).
Also updated the implementation based on the review comments.