refactor: make fuse_amend implementation more convenient for on-premise deployments

[dantengsky]

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

Summary

Since fuse_amend is currently implemented using the AWS Rust SDK, some behaviors may be inconsistent with other components based on OpenDAL, especially in on-premise deployment. e.g.

• Different default TLS cert verification strategy
  For instance, if the HTTPS service's certificate is a CA certificate (rather than an end-entity certificate), OpenDAL (using OpenSSL) will not reject the connection. However, the default configuration of the AWS Rust SDK (using Rustls) will reject such certificates. Other similar issues may also occur.

• The configuration of the endpoint URL may require a more flexible approach in on-premise deployment

  For on-premise deployments of s3-compatible services, the choice of addressing style for buckets may vary (e.g., path-style vs. virtual-hosted-style addressing).

To better accommodate on-premise deployment scenarios, although this PR continues to use the AWS Rust SDK, it forces the usage of an native_tls based HTTPS connector.

Besides, two new settings have been introduced to allow more flexible configuration:

• premise_deploy_danger_amend_accept_invalid_cert

  When set to 1, fuse_amend will accept invalid certificates during execution. The default value is 0.
  This parameter is intended solely for diagnosing issues in on-premise deployments and should not be enabled in production environments.

  When enabled (set to 1), domain name validation will also be skipped.

• premise_deploy_amend_force_path_style

  When set to 1, fuse_amend will use path-style URIs to access buckets during execution. The default value is 1.

Misc:

• Some unused crates are removed
• Verbose error message for list_object_versions failure

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - use existing tests

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