Tech Debt: Happo failures in breadcrumbs [6]

[andrea-williams]

Description of the Tech Debt

We possibly have introduced a regression with our recent changes to breadcrumbs.

A while ago we were encountering lots of issues with E2E/Happo failures on our breadcrumbs, so we put in the time to fix it. However, since we recently implemented a task regarding breadcrumbs, it's possible that we've now introduced a regression in our E2E flakiness.

Specifically, in the Happo screenshots (for all browsers), the Operator name wasn't rendering in the breadcrumb. This was encountered in a PR with no frontend changes.

Marking this as low-ish priority. So far it's been encountered once - might be worthwhile waiting to see if it becomes a regular issue.

Tech Debt Triage

The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.

Risk Value Scoring:

Level	Value
High	3
Medium	2
Low	1

Technical Debt - Risk Types	Level	Value
Business Area Risk - Risk of business area visibility / damage to user experience		1
Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it		1
System Fault Risk - Risk of system errors or application downtime		1
Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time?		1
Time Sink Risk - How much will this tech debt slow the development process down		2
TOTAL SCORE:		6

[shon-button]

@andrea-williams

Registration1 uses @/app/components/navigation/Bread not the modified breadcrumb bciers/libs/components/src/navigation/Bread.tsx