refactor: Update form field components to align with the new design spec

[rfgamaral]

Short description

This PR implements a few changes to adapt some of the form fields to the new form fields spec. Please refer to CHANGELOG.md (or the commit messages) to better understand the changes that were applied.

Tip

Given the number of changes to bring the form field components to parity with the new form fields spec, a commit-by-commit review is recommended.

Warning

Don't be scared by the number of changes, most of them come from the last commit, which is a temporary commit that includes a Reactist build in this PR branch, so that I can pre-emptively open a PR on ui-extensions and todoist-web without having it break our CI checks.

Before merging this PR, I'll remove that commit, and update both ui-extensions and todoist-web with the real package of Reactist v26.

PR Checklist

• Updated docs (storybooks, readme)
• Executed npm run validate and made sure no errors / warnings were shown
• Described changes in CHANGELOG.md
• Bumped version in package.json and package-lock.json (npm --no-git-tag-version version <major|minor|patch>) ref
• Reviewed and approved Chromatic visual regression tests in CI

Versioning

Breaking change, some props were removed from the BaseField component.

[pedroalves0]

I assume that this PR is not meant to completely align the fields with the new design as there are several things missing or different (e.g. tooltips, invalid error state icon, search clear button).

Not sure if you're continuing this work into Q4, but if you are, I suggest creating stories that replicate 1:1 the Figma designs. Easier to review and to confirm that the client implementation follows the mockups.

[rfgamaral]

I assume that this PR is not meant to completely align the fields with the new design as there are several things missing or different (e.g. tooltips, invalid error state icon, search clear button).

The goal was to simplify the components (remove no longer needed things) and to keep them flexible enough to support the new designs (which they do, unless I missed something) from the consumer side.

Not sure if you're continuing this work into Q4(...)

AFAIK, this work will be in the back burner for Q4, and might get picked up some time next year.