fix(feedback): Deep merge custom styles with defaults in FeedbackWidget

[sbs44]

📢 Type of change

• Bugfix

📜 Description

Replace the shallow spread in FeedbackWidget.render() with a dynamic deep merge that iterates over all default style keys. Custom style properties now override individual values while preserving unspecified defaults.

Before (shallow — replaces entire style object):

const styles = { ...defaultStyles(theme), ...this.props.styles };

After (deep — merges per key):

const styles = Object.fromEntries(
  Object.keys(_defaultStyles).map(key => [
    key,
    { ..._defaultStyles[key], ..._propStyles[key] },
  ]),
) as FeedbackWidgetStyles;

💡 Motivation and Context

Fixes #5624 — passing partial style overrides (e.g. styles={{ input: { color: 'red' } }}) currently loses all default properties for that key (height, padding, borderWidth, etc.), breaking layout.

💚 How did you test it?

• Added unit test: render with partial input style override, assert default properties (height, borderWidth, borderRadius, paddingHorizontal, marginBottom, fontSize) are preserved
• Updated existing snapshots to reflect the corrected merge behavior
• All existing tests pass

📝 Checklist

• I added tests to verify changes
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled
• I updated the docs if needed.
• I updated the wizard if needed.
• All tests passing
• No breaking changes

🔮 Next steps

None — this is a self-contained fix.

[github-actions]

Semver Impact of This PR

⚪ None (no version bump detected)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

• fix(feedback): Deep merge custom styles with defaults in FeedbackWidget by sbs44 in #5625

---

_{🤖 This preview updates automatically when you update the PR.}

[lucas-zimerman]

The PR is good, and I'd say it's ready to merge. I just want more opinions from other reviewers if we should consider this a break change, despite being a bugfix.

[lucas-zimerman]

@sentry review

[antonis]

The PR is good, and I'd say it's ready to merge. I just want more opinions from other reviewers if we should consider this a break change, despite being a bugfix.

That's a good point @lucas-zimerman 👍
I think the majority of the users won't face any issues since to overcome the bug/shortcoming of the implementation they had to add all properties. I would suggest just adding an extra note on the changelog like #5625 (comment)
Wdyt?

[lucas-zimerman]

LGTM! Thank you for your contribution!

[antonis]

LGTM 🎸
Thank you for your contribution 🙇