Optimize processResponseCommand in NettyRemotingAbstract by Removing Redundant Operations

[DivyanshIITB]

Key Changes:

• Removed duplicate operation: responseFuture.setResponseCommand(cmd); was being called outside and inside the if condition.
  It is now moved inside the conditional block where getInvokeCallback() != null.
• Enhanced maintainability: Eliminates unnecessary code while preserving the intended behavior.
• No functional impact: The change ensures that setResponseCommand(cmd); is executed only when required.

Why This Change?

• The previous implementation resulted in an unnecessary function call in cases where getInvokeCallback() was null.
• This minor optimization improves performance by avoiding redundant method execution.

Testing & Verification:

• Unit tests were run to verify that the behavior remains consistent.
• The RocketMQ remoting module continues to function as expected.

Fixes #2578

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 20.00000% with 4 lines in your changes missing coverage. Please review.

Project coverage is 48.00%. Comparing base (34c32d8) to head (bac1227).

Files with missing lines	Patch %	Lines
...rocketmq/remoting/netty/NettyRemotingAbstract.java	20.00%	3 Missing and 1 partial ⚠️

Additional details and impacted files

@@              Coverage Diff              @@
##             develop    #9268      +/-   ##
=============================================
- Coverage      48.16%   48.00%   -0.16%     
+ Complexity     12124    12091      -33     
=============================================
  Files           1322     1322              
  Lines          93126    93128       +2     
  Branches       11940    11940              
=============================================
- Hits           44850    44704     -146     
- Misses         42738    42884     +146     
- Partials        5538     5540       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.