Polish Azure parser filtering

Root cause: the last Azure Maps parser cleanup still left one code-quality complaint on the reverse-address mapping loop.

Use a Select-based reverse-address pipeline so the parser stays explicit about filtering and mapping without changing behavior.

Author: niemyjski

src/Geocoding.Microsoft/AzureMapsGeocoder.cs

@@ -257,11 +257,12 @@ private IEnumerable<AzureMapsAddress> ParseResponse(AzureSearchResponse response
         if (response.Addresses is null)
             yield break;
 
-        foreach (var reverseResult in response.Addresses.Where(result => result?.Address is not null && !String.IsNullOrWhiteSpace(result.Position)))
+        foreach (var reverseAddress in response.Addresses
+            .Where(result => result?.Address is not null && !String.IsNullOrWhiteSpace(result.Position))
+            .Select(CreateReverseAddress)
+            .Where(address => address is not null))
         {
-            var reverseAddress = CreateReverseAddress(reverseResult);
-            if (reverseAddress is not null)
-                yield return reverseAddress;
+            yield return reverseAddress!;
         }
     }