Add an InfoStream to ReplicationService to facilitate debugging [LUCENE-9951]

At the moment, when an exception occurs during replication, the ReplicationService tries to serialize it and send it to the client, which then reports it.

This does not work when the exception occurs after the first part of the response has already been sent, or if there was a network error. In these cases, the exception is silently ignored (on the server side), and the client side will report a TruncatedChunkException, making it hard to find the exact cause of the problem.

I propose to add an InfoStream to the ReplicationService (analogous to the ReplicationClient) which will log requests and errors that are sent back to the client.

I will provide a PR for this issue.

---
Migrated from [LUCENE-9951](https://issues.apache.org/jira/browse/LUCENE-9951) by Christoph Kaser
Pull requests: https://github.com/apache/lucene/pull/124

Start by reading ReplicationService and compare its behavior with the analogous ReplicationClient InfoStream. Trace the request and error paths described in the issue; the work is done when server-side requests and errors sent back to the client are logged, including failures after part of a response is sent or after a network error.

Written by the indexing model from the issue text.