Fix picasso-tailwind package.json exports

[augustobmoura]

Description

Describe the changes and motivations for the pull request.

How to test

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

Screenshots

Before.	After.
Insert screenshots or screen recordings	Insert screenshots or screen recordings

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: 856c2bc

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-tailwind	Patch

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]

@toptal-bot run package:alpha-release

[toptal-devbot]

Your alpha package is ready 🎉
yarn add @topkit/analytics-charts@52.0.1-alpha-hotfix-picasso-tailwind-exports-856c2bcc1.70+856c2bcc1
yarn add @toptal/[email protected]+856c2bcc1
yarn add @toptal/picasso-charts@55.1.1-alpha-hotfix-picasso-tailwind-exports-856c2bcc1.32+856c2bcc1
yarn add @toptal/picasso-codemod@5.6.4-alpha-hotfix-picasso-tailwind-exports-856c2bcc1.21+856c2bcc1
yarn add @toptal/picasso-forms@65.0.2-alpha-hotfix-picasso-tailwind-exports-856c2bcc1.41+856c2bcc1
yarn add @toptal/picasso-pictograms@2.0.1-alpha-hotfix-picasso-tailwind-exports-856c2bcc1.91+856c2bcc1
yarn add @toptal/picasso-provider@3.4.2-alpha-hotfix-picasso-tailwind-exports-856c2bcc1.82+856c2bcc1
yarn add @toptal/picasso-query-builder@1.1.3-alpha-hotfix-picasso-tailwind-exports-856c2bcc1.2+856c2bcc1
yarn add @toptal/picasso-rich-text-editor@9.0.2-alpha-hotfix-picasso-tailwind-exports-856c2bcc1.41+856c2bcc1
yarn add @toptal/picasso-shared@13.0.1-alpha-hotfix-picasso-tailwind-exports-856c2bcc1.91+856c2bcc1
yarn add @toptal/picasso-tailwind@0.0.2-alpha-hotfix-picasso-tailwind-exports-856c2bcc1.3936+856c2bcc1