[FX-4492] Remove unwanted tag transitions

[mkrl]

FX-4492

Description

Remove the default transitions from all Tag components.
I was not able to disable them in a single place (in theory, it should be possible to use overrides in PicassoProvider, however, in practice it just didn't work at all, probably due to class overrides inside components).

How to test

• Temploy
• You can use the code below to test the transition, both on master and temploy

import React, { useState } from 'react'
import { Button, Container, Tag } from '@toptal/picasso'

const Example = () => {
    const [type, setType] = useState('red')

    return (
        <Container flex>
            <Button
                onClick={() =>
                    setType(prevType => (prevType === 'green' ? 'red' : 'green'))
                }
                size='small'
            >
                Change color
            </Button>
            <Tag.Rectangular variant={type}>Tag</Tag.Rectangular>
        </Container>
    )
}

export default Example

Screenshots

Before

deepin-screen-recorder_Select.area_20231120121350.mp4

After

deepin-screen-recorder_Select.area_20231120121139.mp4

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
• [n/a] Covered with tests (visual tests included)

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: c4176d5

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

[sashuk]

Tested on temploy, looks great!

[sashuk]

@toptal-anvil ping reviewers