Remove unnecessary locking when commit and rollback transaction

[dai-chen]

What is the bug?

The current transition process from the initial to transient to final metadata log entry is executed using OpenSearch optimistic locking. The transition from initial to transient ensures a single execution thereafter. However, given this assumption, there is no actual need to employ optimistic locking again when committing the transaction to the final state or rolling back to the initial state.

What is the expected behavior?

Eliminate the unnecessary OpenSearch optimistic locking when committing and rolling back the transaction. This adjustment also contributes to a reduction in the likelihood of version conflicts during index monitor updates to the heartbeat.