fix: ButtonLink onClick handler

[nhsz]

This PR updates the ButtonLink component to handle custom onClick events and override its behavior when needed. Fixes the issue of /wallets/find-wallet/ Visit website CTA not being tracking the event when clicked.

Testing

• Go to /wallets/find-wallet/ now the Visit website button should be triggering the custom handleWalletWebsiteClick event handler
• Go to any other page like /community/ to check that the ButtonLink component is still working as expected for other cases

Preview

https://deploy-preview-12935--ethereumorg.netlify.app/wallets/find-wallet

[netlify]

✅ Deploy Preview for ethereumorg ready!

Name	Link
🔨 Latest commit	82e3280
🔍 Latest deploy log	https://app.netlify.com/sites/ethereumorg/deploys/663e80445638220008be92dc
😎 Deploy Preview	https://deploy-preview-12935--ethereumorg.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	7 paths audited Performance: 52 (🔴 down 4 from production) Accessibility: 92 (no change from production) Best Practices: 94 (🔴 down 4 from production) SEO: 95 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[wackerow]

Hm.. this is a little confusing since we're accepting an onClick, which could override the click handler per below, but we also have customEventOptions which wouldn't be used if onClick is provided...

@nhsz If we need to accept onClick here, should we merge it into the handleClick() function below? ie

const handleClick = () => {
  customEventOptions && trackCustomEvent(customEventOptions)
  onClick()
}

[pettinarip]

@nhsz @wackerow the underlying Button component already handles this logic. So I'd say, let's get rid of the onClick handler from this component completely and rely on the logic set in the button component. Otherwise, we are (and we were) duplicating this logic.

[pettinarip]

@nhsz @wackerow the underlying Button component already handles this logic. So I'd say, let's get rid of the onClick handler from this component completely and rely on the logic set in the button component. Otherwise, we are (and we were) duplicating this logic.