Duchy fails to create final MeasurementLogEntry for succeeded Measurement

[SanjayVas]

Reported by Dmitry Makarevich.

This fails with Cannot create log entry for Measurement in terminal state.

The Duchy shouldn't be making this as a separate call after completing the Measurement, as indeed it is incorrect to add a log entry after this point. This log entry may not even be needed, as there's already one automatically created for the state transition.

org.wfanet.measurement.kingdom.deploy.gcloud.spanner.common.MeasurementStateIllegalException: Cannot create log entry for Measurement in terminal state. {external_measurement_consumer_id=ExternalId(2072627392850428159 / HMNzoe6YAP8), external_measurement_id=ExternalId(6975708498392167955 / YM6x659WthM), measurement_state=SUCCEEDED}
	at org.wfanet.measurement.kingdom.deploy.gcloud.spanner.writers.CreateDuchyMeasurementLogEntry.runTransaction(CreateDuchyMeasurementLogEntry.kt:70)
	at org.wfanet.measurement.kingdom.deploy.gcloud.spanner.writers.CreateDuchyMeasurementLogEntry$runTransaction$1.invokeSuspend(CreateDuchyMeasurementLogEntry.kt)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33)
	at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:749)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)