chore: make error message of conflicting transactions more user-friendly

[SkyFan2002]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

revelant issue: #17306

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

---

This change is 

[what-the-diff]

PR Summary

• Improved System Transparency
  The team has added a new logging feature to record issues that may occur during the final steps of processing transactions. This will help us quickly identify and rectify any potential bottlenecks or conflicts.

• Better Error Communication in Catalog Updates
  They have fine-tuned the system's error messages when updating multiple-table metadata in the Catalog. Now, it can precisely communicate any issues related to conflicting table IDs, which could happen when multiple transactions are happening simultaneously.

• Refined Error Management During Transaction Finalization
  The process of transaction finalization has been improved as well. Previously, if there were version mismatches in tables, it could lead to transaction failures. Now, the system will provide more detailed information about such issues to help diagnose, and subsequently resolve, these more swiftly.