Inconsistent behaviour with Hive Locking + connection lost to metastore

[Noremac201]

• Hive Metastore 3.1.x
• Trino >= 477

This pull request removes the expected param check from Hive Metastore. This is fine, as it's not technically needed, HOWEVER, there is a scenario where if Iceberg retries the request, after the first one had been successfully ack'ed by the Hive Metastore it will clobber any more data written.

This failure scenario is now possible explicitly because we are not checking that the data has been modified in Hive Metastore without this env context.

PR that introduced this behaviour: #26358

See apache/iceberg#14096 for more information as well on failure scenario.