[FX-4598] Migrate Notification to TailwindCSS

[AdrianContiu]

FX-4598

Description

This PR changes the Notification component to use the Snackbar from the MUI Base UI and applies styles using TailwindCSS.

Note:

• There is also a change of the role attribute from alert to presentation. This was done due to an issue with the screen reader in Firefox. More details can be found here. It will also be included in the changeset file.
• failed Happo tests are because the feature branch is out of date.

How to test

• Temploy
• Check the production and compare it with the temploy

Screenshots

Before.	After.
	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: 7d58f0d

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

This PR includes changesets to release 5 packages

Name	Type
@toptal/picasso-notification	Major
@toptal/picasso-forms	Patch
@toptal/picasso-query-builder	Patch
@toptal/picasso	Patch
@toptal/picasso-page	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

[OleksandrNechai]

I am concerned with twMerge usage, and !. When those are fixed or proven needed, I am good to go!

[toptal-devbot]

⚠️ Following packages are missing changesets. Please check if they don't require one.

@toptal/picasso-utils