RATIS-872. Invalidate replied calls in retry cache.

[szetszwo]

See RATIS-872.

[szetszwo]

The test failure is related: https://github.com/apache/ratis/actions/runs/6566630497/job/17837715966?pr=942#step:5:811

Since the calls are submitted asynchronously, we cannot assume the callIds are in order. Will remove the callId set from the server side and let the client send multiple replied callIds.

[SzyWilliam]

Thanks @szetszwo for the retry cache optimization! The change looks good to me.
Just a small question, since we do not carry repliedId for read-only requests in unorderedAsync, shall we also exclude them in orderedAsync?

[szetszwo]

..., since we do not carry repliedId for read-only requests in unorderedAsync, shall we also exclude them in orderedAsync?

This is a very good question! I handle blocking call and async calls separately. Actually, it is better to handle all the calls at the same time in RaftClientImpl, which will collect the replied call ids and use them to create requests. Let me update this after RATIS-1916.

[szetszwo]

@SzyWilliam , moved all the replied callId handling to RaftClientImpl and any calls can include replied callIds.

[SzyWilliam]

Sorry I missed out the update. +1 the change looks good. The code looks really neat!

[szetszwo]

@SzyWilliam , thanks a lot for reviewing and merging this!