Inconsistent Confirm Bug?

When an IR replica receives a FinalizeInconsistentMessage message from a client, it responds with a ConfirmMessage (see here). However, the client seems to be only expecting ConfirmMessages for consensus operations (see here).

I'm happy to help fix this bug, but I wasn't sure what the right fix is. The TAPIR paper doesn't mention replicas sending confirmations for inconsistent operations, so one possibility is to have replicas not send confirmations for them. Or, we could just fix IRClient::HandleConfirm to expect confirmations for both inconsistent and consensus operations.