[Tag]: new TEDI-Ready component

[mart-sessman]

Design:
https://www.figma.com/design/jWiRIXhHRxwVdMSimKX2FF/TEDI-READY-2.30.43?node-id=5784-114505&m=dev

DoD

• The component is developed using best practices, conventions, and modern frontend trends
• The component follows BEM naming conventions (if applicable)
• The component implementation matches the Figma design, including all defined states and interactions
• The component supports responsiveness and scales across breakpoints (if applicable)
• The component does not introduce runtime errors or warnings
• Linter passes
• Component has export if needed
• The component has unit tests with at least 80% code coverage
• CodeCov passes minimum coverage threshold
• The component has passed code review
• The component has passed Chromatic visual review
• Storybook stories are created:
  • Cover all Figma variations
  • Include edge cases, empty/error states
• Component’s API (props, slots, events) is documented
• ZeroHeight is updated with design/development guidelines
• External dependencies used in the component are documented in Confluence with rationale.
• Semantic commit format is used (for semantic-release)
• External libraries comply with validated open source licenses
• Component is versioned correctly and ready for release if required
• Update statuses page in Zeroheight

[mart-sessman]

Story for design review: https://storybook.tedi.ee/angular/feat/297-tag-tedi-ready-component/?path=/docs/tedi-ready-components-tags-tag--docs

[karolin-kivisikk]

Desgin review:

1. Different stories are shown from React, update React against the Angular or update Angular against React. With every component development we should keep in mind other dev framework so the examples would look as same as possible.
2. First example content is also different from React example.
3. Close button should be adjusted according to tag shape, see React examples or from Figma