Add concurrent writes reconciliation for UPDATE/MERGE/DELETE in Delta Lake

[findinpath]

Description

Spin-off from #18521

Allow committing operations based on:

• merge mechanism (applies for regular UPDATE/DELETE/MERGE statements)

in a concurrent context by placing these operations right after
any other previously concurrently completed write operations.

Disallow committing the operation in any of the following cases:

• table schema change has been committed in the meantime
• table protocol change has been committed in the meantime
• add files committed in the meantime should be read by
  the current operation
• remove files committed in the meantime conflict with the
  add files read by the current operation

The current changes also take into consideration the delta.isolationLevel
table property of the Delta Lake table for UPDATE/DELETE/MERGE operations.

Relevant example taken from Databricks documentation in regards to the
distinction between WriteSerializable and Serializable isolation levels:

For example, consider txn1, a long running delete and txn2,
which inserts blindly data into the table.
txn2 and txn1 complete and they are recorded in the order
txn2, txn1
into the history of the table.
According to the history, the data inserted in txn2 should not exist
in the table. For Serializable level, a reader would never see data
inserted by txn2. However, for the WriteSerializable level, a reader
could at some point see the data inserted by txn2.

A few words about WriteSerializable isolation level taken from delta.io javadocs:

This isolation level will ensure snapshot isolation consistency guarantee
between write operations only.
In other words, if only the write operations are considered, then
there exists a serializable sequence between them that would produce the same
result as seen in the table.

Additional context and related issues

INSERT scaffolding PRs:

• Add concurrent writes reconciliation for blind append INSERT in Delta Lake #18506
• Add concurrent writes reconciliation for non-blind INSERT in Delta Lake #20983

Spin-off from #18521

Release notes

( ) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
(x) Release notes are required, with the following suggested text:

# Delta Lake
* Add support for concurrent `UPDATE`,`MERGE` and `DELETE` queries. ({issue}`issuenumber`)

[ebyhr]

/test-with-secrets sha=04d7fde3bbb30b242b07acbbba1a00b0f04dd3ee

[github-actions]

The CI workflow run with tests that require additional secrets finished as failure: https://github.com/trinodb/trino/actions/runs/9294322023