feat: deprecate legacy s3 connector

[tabVersion]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

resolve #16234

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Edited by @neverchanje
The only available s3 connector is now s3_v2. s3 is deprecated and should not appear in the document.

[neverchanje]

How about just refuse the requests for s3 connector and tell them use s3_v2 instead.

A little bit weird but OK for the short-term.

[tabVersion]

cc @BugenZhao as introducing new item in RwErrorCode

[xxchan]

I think main-cron ci tests will fail. Perhaps you will want to remove them.

[tabVersion]

maid cron failed on an irrelevant hummock test, merging now
https://buildkite.com/risingwavelabs/main-cron/builds/2380