EPIC: Stand component library discovery

**Exploring to what degree we can use the Stand component library to build notifications tooling UX/UI.**

**Context**
Work on the current internal GU tools design system is providing a quality gate reference for the build of all future internal tooling -_[Reference: Building An Internal Design System for Guardian Tools](https://docs.google.com/document/d/1WqImgTWArPShO5sgbzFc2sZ2lg26IHknsyR7Y6T8jn0/edit?tab=t.0#heading=h.cebepnqtgn7o)_

While the current notification prototype provides a baseline for what end users may expect e.g. sending a breaking news alert, it is not fully understood to what degree the underlying source code meets the GU standards.

The aim of the stories/tasks within this EPIC is to understand whether the internal design system can be utilised to bridge any gaps in quality from the baseline prototype, or if we need to progress closer to shared component libraries that will be used across future tooling dev.

**Ideas**
- [ ] Review Stand component library _as is_
- [ ] Review Stand component library _roadmap_
- [ ] Map existing Stand components elements to those present in the prototype
- [ ] Review gaps for missing Stand components across breaking news user journey.
- [ ] Share findings with the design system team.

Start by reviewing the Stand component library as-is and its roadmap, then compare its components with those used in the breaking-news notification prototype. Done means the component mapping and gaps across the user journey are documented and the findings are shared with the design system team.

Written by the indexing model from the issue text.