fix: use haze for secondary button bg blur

[ovitrif]

Description

Stacked on:

• fix: polish buttons to match figma design #887

This PR replaces the custom glassBlur modifier on SecondaryButton with the Haze library's frosted glass blur effect. The old glassBlur used BlurMaskFilter which only blurred the drawn tint shape itself — it never actually blurred the background content behind the button. Now the button uses Haze's hazeEffect with a custom HazeStyle to produce a real frosted glass blur matching the Figma design.

Key changes:

1. Adds a hazeState parameter to SecondaryButton for opt-in background blur
2. Wraps OutlinedButton in a clipped Box so the blur renders before Material's Surface
3. Sets up hazeSource on the background layer of Spending and Savings wallet screens
4. Removes the dead glassBlur modifier, GlassBlurElement, and GlassBlurNode
5. Removes unused secondaryBlurRadius from ButtonSize

Preview

Figma vs Screenshot

Secondary Button Preview
Android Studio Render

QA Notes

1. Open Spending wallet screen with a balance and channels
   • Verify the "Transfer To Savings" button shows a subtle frosted glass blur of the background coin stack image
   • Verify the button has rounded corners on the blur effect
2. Open Savings wallet screen with a balance
   • Verify the "Transfer To Spending" button shows a similar frosted glass blur of the piggybank image
3. Check onboarding screens that use SecondaryButton (Intro, Create Wallet, Restore)
   • Verify buttons render normally without blur (no crash)
4. Optional: Check SecondaryButtonPreview in Android Studio

[ovitrif]

@claude Please make a table listing all screens using Secondary Button, and on the 2nd column with a checkbox ✅ or cross ❌ if it it uses hazeState (ie. should blur) or not.

[ovitrif]

@jvsena42 can we merge it back to target PR and you can do your investigation there if you're still keen to pursue it?

• fix: use haze for secondary button bg blur #890 (comment)

I didn't use a Box because in the past caused some bugs either from fullWidth or from .weight(1f) in the PrimaryButton when used for the gradient effect.

I'll check some screens and see if this caused some regression

Either do your investigation as you planned, or if you remember where it might've exploded, delegate to me as author of these changes, I'll bring the receipts if it works or not, after testing manually.