compare silent payment scan addresses when considering wallet address changes

What changed, and why it matters

This commit fixes a logic gap in Sparrow Wallet's settings form. When a user changes wallet settings, the app checks whether the wallet's receiving addresses would change, so it can warn or take appropriate action. The check already compared regular extended public keys, but it forgot to compare 'silent payment scan addresses'—a newer Bitcoin privacy feature. Without this comparison, changing the silent-payment scan key might not be detected as an address change, potentially causing the wallet to show stale or incorrect addresses without warning.

Security signals we found

Evidence from the diff

Changed components

### src/main/java/com/sparrowwallet/sparrow/wallet/SettingsWalletForm.java
@@ -197,6 +197,10 @@ private boolean isAddressChange(Wallet original, Wallet changed) {
             if(!Objects.equals(originalKeystore.getExtendedPublicKey(), changedKeystore.getExtendedPublicKey())) {
                 return true;
             }
+
+            if(!Objects.equals(originalKeystore.getSilentPaymentScanAddress(), changedKeystore.getSilentPaymentScanAddress())) {
+                return true;
+            }
         }
 
         return false;