Remove ERROR level log on failed no-ops

[alecgrieser]

Right now, we log at ERROR if there is a failure when performing a no-op, even though we propagate the error. See:

fdb-record-layer/fdb-record-layer-core/src/main/java/com/apple/foundationdb/record/provider/foundationdb/FDBDatabase.java

Lines 482 to 487 in d19f7b2

	private void logNoOpFailure(@Nonnull Throwable err) {
	if (LOGGER.isErrorEnabled()) {
	LOGGER.error(KeyValueLogMessage.of("unable to perform no-op operation against fdb",
	LogMessageKeys.CLUSTER, getClusterFile()), err);
	}
	}

However, this is a bit misleading, for a few reasons:

1. No-ops can fail, and it shouldn't be classified as an ERROR. The most likely reason for this is that when the client is starting up (if using the multi-version client), then a no-op can fail with "cluster version changed".
2. The error is getting propagated up anyway. The only additional information is maybe what cluster is being used, which may be helpful in a world where different clusters are configured to use different network threads.

We should be able to remove this ERROR-level log and replace it with something that adds the cluster to the error log info. Then clients can decide at what level they want to log this, rather than potentially polluting their logs with (ultimately) spurious errors.