[Enhancement] configure S3 client rename_file operation timeout (backport #48860)

[mergify]

Why I'm doing:

Currently, sr use object_storage_request_timeout_ms as the S3 client request timeout. But this parameter maybe too small in some case especially using by rename_file operation for large file (1GB, for example). Timeout maybe happen in this case

What I'm doing:

We introduce a new BE/CN config called object_storage_rename_file_request_timeout_ms and it is used as following:

1. If object_storage_rename_file_request_timeout_ms >= 0, it will used for rename_file operation in S3 as the request timeout.
2. If object_storage_rename_file_request_timeout_ms < 0, the timeout limit for rename_file operation in S3 will be determinded by object_storage_request_timeout_ms.

Fixes #issue

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.3
  • 3.2
  • 3.1
  • 3.0
  • 2.5

---

This is an automatic backport of pull request #48860 done by [Mergify](https://mergify.com). ## Why I'm doing: Currently, sr use object_storage_request_timeout_ms as the S3 client request timeout. But this parameter maybe too small in some case especially using by rename_file operation for large file (1GB, for example). Timeout maybe happen in this case

What I'm doing:

We introduce a new BE/CN config called object_storage_rename_file_request_timeout_ms and it is used as following:

1. If object_storage_rename_file_request_timeout_ms >= 0, it will used for rename_file operation in S3 as the request timeout.
2. If object_storage_rename_file_request_timeout_ms < 0, the timeout limit for rename_file operation in S3 will be determinded by object_storage_request_timeout_ms.

Fixes #issue

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr