feat: implement style api for text filter component

[mxschll]

Description

Extends the text filter component with a style API for customization, allowing developers to override default component styles.

Related links, issue #, if available: n/a

How has this been tested?

• Added unit tests for style prop validation and CSS class application
• Screenshot tests passed without visual regressions

Review checklist

The following items are to be evaluated by the author(s) and the reviewer(s).

Correctness

• Changes include appropriate documentation updates.
• Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
• Changes do not include unsupported browser features, see CONTRIBUTING.md.
• Changes were manually tested for accessibility, see accessibility guidelines.

Security

• If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

• Changes are covered with new/existing unit tests?
• Changes are covered with new/existing integration tests?

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.12%. Comparing base (f796951) to head (7b5144a).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4050      +/-   ##
==========================================
+ Coverage   97.00%   97.12%   +0.11%     
==========================================
  Files         862      863       +1     
  Lines       25290    25292       +2     
  Branches     9123     9120       -3     
==========================================
+ Hits        24532    24564      +32     
+ Misses        752      681      -71     
- Partials        6       47      +41     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[cansuaa]

I see slightly different implementations in styles.tsx files. E.g. in prompt input we filter out the undefined values, why aren't we doing the same here?

[mxschll]

Yea because of this comment: #4025 (comment)

[cansuaa]

I see, then we should remove that logic from prompt input as well

[mxschll]

Yes, I'll open a subsequent PR for that if that's ok?

[cansuaa]

Yes, also in the PR linked I don't see matchSnapshot being used but it is used here. Why are there different implementations? Let's have consistency across these similar implementations