Migrated wrapField tests to @testing-library/react

[zaxovaiko]

Is part of #1130

[piotrpospiech]

This PR really points out the disadvantage of the suites approach (the same as SelectField suites, I guess)

1. We talked we don't want to create flags for specific themes, but I see why it is needed here.
2. Creating tests only for one theme in the suite or changing the expect check for the specific theme only makes this suite harder to read.

I think we need to consider keeping theme-specific tests in a separate file. We could keep core tests in the suites and keep theme specific in the theme package or create a separate file (we can have wrapField as a directory). The distinction can be necessary as we support different props, e.g., validateStatus in the AntD theme.

The same issue is true for the rest of the tests that are waiting to be moved to suites (mainly AntD and MUI).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.32%. Comparing base (4b3f109) to head (0b739ca).
Report is 6 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1318      +/-   ##
==========================================
- Coverage   94.55%   94.32%   -0.24%     
==========================================
  Files         231      229       -2     
  Lines        3823     3754      -69     
  Branches     1030     1011      -19     
==========================================
- Hits         3615     3541      -74     
+ Misses         82       81       -1     
- Partials      126      132       +6     

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