[Storage] Fix listener to use the target data blob client over the host (#50431)

* Fix listner to use the target data blob client over the host

* Removing unneccessary variable

* Changelog

Author: amnguye

sdk/storage/Microsoft.Azure.WebJobs.Extensions.Storage.Blobs/CHANGELOG.md

@@ -7,6 +7,7 @@
 ### Breaking Changes
 
 ### Bugs Fixed
+- Fixed bug where the scan will continue scanning AzureWebJobsStorage even when configuring a target storage account
 
 ### Other Changes
 

sdk/storage/Microsoft.Azure.WebJobs.Extensions.Storage.Blobs/src/Listeners/BlobListenerFactory.cs

@@ -87,8 +87,6 @@ public async Task<IListener> CreateAsync(CancellationToken cancellationToken)
         {
             // Note that these clients are intentionally for the storage account rather than for the dashboard account.
             // We use the storage, not dashboard, account for the blob receipt container and blob trigger queues.
-            var primaryBlobClient = _hostBlobServiceClient;
-
             // Important: We're using the storage account of the function target here, which is the account that the
             // function the listener is for is targeting. This is the account that will be used
             // to read the trigger blob.
@@ -107,7 +105,7 @@ public async Task<IListener> CreateAsync(CancellationToken cancellationToken)
                     new SharedBlobListenerFactory(hostId, _hostBlobServiceClient, _exceptionHandler, _blobWrittenWatcherSetter, _loggerFactory.CreateLogger<BlobListener>()));
 
                 // Register the blob container we wish to monitor with the shared blob listener.
-                await RegisterWithSharedBlobListenerAsync(hostId, sharedBlobListener, primaryBlobClient,
+                await RegisterWithSharedBlobListenerAsync(hostId, sharedBlobListener, targetBlobClient,
                     blobTriggerQueueWriter, cancellationToken).ConfigureAwait(false);
             }