DAOS-19059 vos: cache vos object after DTX commit

It is unnecessary to evict the vos object from cache after related
DTX committed; otherwise, other concurrent modification against the
same object shard maybe required to retry.

Signed-off-by: Fan Yong <fan.yong@hpe.com>

Author: Nasf-Fan

src/vos/vos_dtx.c

@@ -2687,6 +2687,8 @@ vos_dtx_post_handle(struct vos_container *cont,
 	}
 
 	for (i = 0; i < count; i++) {
+		struct vos_dtx_act_ent *dae = NULL;
+
 		if (daes[i] == NULL)
 			continue;
 
@@ -2703,9 +2705,12 @@ vos_dtx_post_handle(struct vos_container *cont,
 		}
 
 		d_iov_set(&kiov, &DAE_XID(daes[i]), sizeof(DAE_XID(daes[i])));
-		rc = dbtree_delete(cont->vc_dtx_active_hdl, BTR_PROBE_EQ,
-				   &kiov, NULL);
+		rc = dbtree_delete(cont->vc_dtx_active_hdl, BTR_PROBE_EQ, &kiov,
+				   abort ? NULL : &dae);
 		if (rc == 0 || rc == -DER_NONEXIST) {
+			if (dae != NULL)
+				D_ASSERT(dae == daes[i]);
+
 			dtx_evict_lid(cont, daes[i]);
 		} else {
 			/* The DTX entry has been committed or aborted, but we