Fix infinite loop in AzureObjectStorage::listObjects

[jkartseva]

The loop calls client_ptr->ListBlobs(options) inside the body on every iteration, overwriting blob_list_response with the first page.
This cancels out the pagination logic (MoveToNextPage()) in the loop. If the first page returns HasPage() == true, for example, when the first page is empty, this leads to an infinite loop:
https://pastila.clickhouse.com/?00079d20/bac6ffc01386edeba163db1798cf2832#zb4gt9R5wmh4zOzbk3PbeA==

Azurite does not reproduce this.
I’ve tried to reproduce the bug using gtest mocks (e.g., for the AzureBlobStorage::ContainerClient), but haven’t succeeded yet.

For reference, the SDK demonstrates blob iteration as follows:
https://github.com/ClickHouse/azure-sdk-for-cpp/blob/0f7a2013f7d79058047fc4bd35e94d20578c0d2b/sdk/storage/azure-storage-blobs/test/ut/blob_container_client_test.cpp#L299-L306

Changelog category (leave one):

• Bug Fix (user-visible misbehavior in an official stable release)

Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):

Fix possible infinite loop in azure list blobs.

Documentation entry for user-facing changes

• Documentation is written (mandatory for new features)

[clickhouse-gh]

Workflow [PR], commit [a4957d0]

Summary: ❌

job_name	test_name	status	info	comment
Stateless tests (arm_asan, targeted)		failure
	00446_clear_column_in_partition_concurrent_zookeeper	FAIL	cidb
	00446_clear_column_in_partition_concurrent_zookeeper	FAIL	cidb
	00446_clear_column_in_partition_concurrent_zookeeper	FAIL	cidb
	00446_clear_column_in_partition_concurrent_zookeeper	FAIL	cidb
	00446_clear_column_in_partition_concurrent_zookeeper	FAIL	cidb
	00446_clear_column_in_partition_concurrent_zookeeper	FAIL	cidb
	00446_clear_column_in_partition_concurrent_zookeeper	FAIL	cidb
	00446_clear_column_in_partition_concurrent_zookeeper	FAIL	cidb
	00446_clear_column_in_partition_concurrent_zookeeper	FAIL	cidb
Stateless tests (amd_binary, old analyzer, s3 storage, DatabaseReplicated, parallel)		failure
	00075_shard_formatting_negate_of_negative_literal	FAIL	cidb
	03321_inner_materialized_view_nested	FAIL	cidb
	Fatal messages (in clickhouse-server.log or clickhouse-server.err.log)	FAIL	cidb
Stateless tests (amd_msan, parallel)		failure
	00596_limit_on_expanded_ast	FAIL	cidb, flaky
Integration tests (amd_binary, 3/5)		failure
	test_refreshable_mat_view_replicated/test.py::test_real_wait_refresh[to_clause0-False-False]	FAIL	cidb, flaky
Integration tests (amd_binary, 4/5)		failure
	test_refreshable_mv_skip_old_temp_table_ddls/test.py::test_refreshable_mv_skip_old_temp_tables_ddls[1-True-False]	FAIL	cidb, flaky
Integration tests (amd_binary, 5/5)		failure
	test_merge_tree_s3/test.py::test_merge_canceled_by_s3_errors[node-broken_s3]	FAIL	cidb, flaky
BuzzHouse (amd_debug)		failure
	Logical error: 'Inconsistent AST formatting: the query:	FAIL	cidb
BuzzHouse (amd_ubsan)		failure
	UndefinedBehaviorSanitizer: undefined behavior (STID: 1486-329a)	FAIL	cidb
Performance Comparison (amd_release, master_head, 2/6)		failure
	Start	failure
Performance Comparison (amd_release, master_head, 3/6)		failure
	Start	failure

[kssenii]

To be honest I do not understand how it worked before at all, it looks like because of this blob_list_response override inside the loop we always listed only the first page and never went to the next one?