fix: allow label on FieldWrapper to be ReactNode

[OleksandrNechai]

FX-4318

Description

Users want to be able to do complex things with labels, like for example have in label icon and Tooltip. For this we change label type on FieldWrapper from string to ReactNode

How to test

• Temploy
• FIXME: Add the steps describing how to verify your changes

Development checks

• Add changeset according to guidelines (if needed)
• Read CONTRIBUTING.md and Component API principles
• Make sure that additions and changes on the design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
• Annotate all props in component with documentation
• Create examples for component
• Ensure that deployed demo has expected results and good examples
• Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
• Self reviewed
• Covered with tests (visual tests included)

Breaking change

• codemod is created and showcased in the changeset
• test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

• @toptal-bot run package:alpha-release - Release alpha version
• @toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅

You are OK with merging this PR and

1. You have no extra requests.
2. You have optional requests.
   1. Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌

You are not OK with merging this PR because

1. Something is broken after the changes.
2. Acceptance criteria is not reached.
3. Code is dirty.

When to comment (neither ✅ nor ❌)

You want your comments to be addressed before merging this PR in cases like:

1. There are leftovers like unnecessary logs, comments, etc.
2. You have an opinionated comment regarding the code that requires a discussion.
3. You have questions.

How to handle the comments?

1. An owner of a comment is the only one who can resolve it.
2. An owner of a comment must resolve it when it's addressed.
3. A PR owner must reply with ✅ when a comment is addressed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 09972ec

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@toptal/picasso-forms	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[augustobmoura]

Maybe we should also have a example on Storybook about this new funcionality, wdyt?
Also to have some visual tests for it

[sashuk]

Code looks good, tested locally! Having story and visual test as suggested #3856 (review) would be great

[OleksandrNechai]

@sashuk @augustobmoura, @dmaklygin has discovered that FieldWrapper is the thing that we need to deprecate actually. It is not used any more in Picasso. But still used externally and we do this change for suffering people. Most likely we will delete it soon. So I guess no need to put more efforts into it to cover with tests. Ticket for future investigation of FieldWrapper future: https://toptal-core.atlassian.net/browse/FX-4335

[OleksandrNechai]

@toptal-anvil ping reviewers