fix(banking): keep the native green Wise logo, not the aggregator's (#590)

## Context

Follow-up to #589. In production, the deduped Wise entry rendered with
the **Enable Banking blue wordmark** instead of our own green "W" mark,
even though clicking it correctly starts our native (personal-token)
integration.

## Cause

#589 set the native Wise provider's `logo` to the Enable Banking brand
URL (`https://enablebanking.com/brands/BE/Wise/`) and deleted our local
asset — based on the mistaken belief that the green mark came from the
aggregator. It was the other way around: our asset
(`public/images/banks/logos/wise.png`, added in #525) **was** the green
mark; the Enable Banking URL serves the old blue wordmark.

## Fix

- Restore the green Wise asset.
- Point the native provider's `logo` back at
`/images/banks/logos/wise.png`.
- Update the regression test's expected logo accordingly.

Only the `logo` field was ever wrong — the dedup and unique-key fixes
from #589 are unaffected, so a single Wise entry still surfaces our
native integration.

resources/js/components/open-banking/connect-account-dialog.test.tsx

@@ -209,7 +209,7 @@ describe('ConnectAccountDialog', () => {
         const wiseButton = screen.getByRole('button', { name: 'Wise' });
         expect(wiseButton.querySelector('img')).toHaveAttribute(
             'src',
-            'https://enablebanking.com/brands/BE/Wise/',
+            '/images/banks/logos/wise.png',
         );
     });
 

resources/js/lib/connect-providers.tsx

@@ -184,7 +184,7 @@ export const CONNECT_PROVIDERS: ConnectProvider[] = [
         institution: {
             name: 'Wise',
             country: 'ALL',
-            logo: 'https://enablebanking.com/brands/BE/Wise/',
+            logo: '/images/banks/logos/wise.png',
             maximum_consent_validity: null,
         },
         endpoint: '/open-banking/wise/connect',