Enhance Flint error handling with detailed exception messages

[dai-chen]

Description

This PR enhances the error handling capabilities of the FlintSpark class by improving the exceptions thrown during transaction operations. The new error handling approach includes root cause information, making it easier to diagnose and resolve issues.

Changes

• Introduced the withTransaction method to centralize logging and exception handling across different operations within FlintSpark. This method standardizes transaction control and error reporting, reducing code redundancy and enhancing readability.
• Reworked the error handling within the withTransaction method to include detailed root cause information in exceptions. When an operation fails, the catch block now enriches the thrown exceptions with clear, actionable error messages that explain why the operation failed.

Testing

Index state doesn't satisfy the precondition

Tested index state exception for #201:

# Before the changes
java.lang.IllegalStateException: Failed to vacuum Flint index

# After the changes
java.lang.IllegalStateException: Failed to execute index operation [Vacuum Flint index
flint_myglue_ds_tables_http_logs_skipping_index] caused by:
Index state [refreshing] doesn't satisfy precondition

OpenSearch exception

Tested OpenSearch exception for #252:

# Simulate by setting cluster to read only mode:
PUT _cluster/settings
{
   "persistent":{
      "cluster.blocks.read_only": true
   }
}

spark-sql> CREATE INDEX all ON myglue.ds_tables.http_logs (status);

# Before the changes
java.lang.IllegalStateException: Failed to create Flint index

# After the changes
java.lang.IllegalStateException: Failed to execute index operation [Create Flint index
flint_myglue_ds_tables_http_logs_all_index with ignoreIfExists false] caused by:
OpenSearch exception [type=cluster_block_exception, reason=blocked by:
[FORBIDDEN/6/cluster read-only (api)];]

Issues Resolved

• [META] Improve error messaging and exception handling #281
• [BUG]Create MV fails setting up correctly #140
• [FEATURE] Error message is not meaning full, "Fail to run query, cause: Failed to refresh Flint index" #201
• [FEATURE] Creating an index fails with OpenSearch Carbon domain, and the error message is not meaningful. #252

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[dai-chen]

We need to confirm whether any underlying error messages should be hidden from users for security reasons.

1. If confirmed, we will hide these messages.
2. Alternatively, we extract only the root cause message for known exceptions, such as those from OpenSearch or our own Flint exceptions (custom exception class).

@penghuo @vamsi-amazon