feat(connector): support azblob file source

[wcy-fdu]

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

What's changed and what's your intention?

As title, aligned with risingwave-cloud.

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)

Release note

Add azblob file source, which is parallel to the existing s3 source, gcs source

[hzxa21]

LGTM.

For all the newly supported backend for file source and sink, we need to certify that it can work from correctness, stability and security points of view via testing before we can release them officially to our user.

cc @st1page I think we can make them a preview feature first.

[wcy-fdu]

LGTM.

For all the newly supported backend for file source and sink, we need to certify that it can work from correctness, stability and security points of view via testing before we can release them officially to our user.

cc @st1page I think we can make them a preview feature first.

The newly added source and sink pr will be merged after I test it locally. But we will not test all file sink connector in CI or main-cron(gcs, azblob, etc. are not included in ci, only a minio connector is used for e2e test), as they are the same implementation, so I think test the connectivity locally is enough.