Refactoring near azure blob storage

[CurtizJ]

Changelog category (leave one):

• Not for changelog (changelog entry is not required)

Modify your CI run

NOTE: If your merge the PR with modified CI you MUST KNOW what you are doing NOTE: Checked options will be applied if set before CI RunConfig/PrepareRunConfig step

Include tests (required builds will be added automatically):

• [ ] Fast test
• [x] Integration Tests
• [ ] Stateless tests
• [ ] Stateful tests
• [ ] Unit tests
• [ ] Performance tests
• [ ] All with ASAN
• [ ] All with TSAN
• [ ] All with Analyzer
• [x] All with Azure
• [ ] Add your option here

Exclude tests:

• [ ] Fast test
• [ ] Integration Tests
• [ ] Stateless tests
• [ ] Stateful tests
• [ ] Performance tests
• [ ] All with ASAN
• [ ] All with TSAN
• [ ] All with MSAN
• [ ] All with UBSAN
• [ ] All with Coverage
• [ ] All with Aarch64
• [ ] Add your option here

Extra options:

• [ ] do not test (only style check)
• [ ] disable merge-commit (no merge from master before tests)
• [ ] disable CI cache (job reuse)

Only specified batches in multi-batch jobs:

• [ ] 1
• [ ] 2
• [ ] 3
• [ ] 4

[CurtizJ]

The idea of refactoring is to unify creation of client in azure disk and in azure storage.

[robot-clickhouse-ci-1]

This is an automated comment for commit 7f2bfc5f14aeca850c7a82f184ae7812219b91b1 with description of existing statuses. It's updated for the latest CI running

❌ Click here to open a full report in a separate page

Check name	Description	Status
Stateless tests	Runs stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	❌ failure

Successful checks

Check name	Description	Status
Flaky tests	Checks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integration tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc	✅ success
Integration tests	The integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests	✅ success
Stress test	Runs stateless functional tests concurrently from several clients to detect concurrency-related errors	✅ success
Style check	Runs a set of checks to keep the code style clean. If some of tests failed, see the related log from the report	✅ success

[CurtizJ]

The PR has failed: too many conflicts. Basically it's required to reimplement it from scratch.

[CurtizJ]

Test 00002_log_and_exception_messages_formatting is failed in master with azure.