Testing labelling DO NOT MERGE

[georgewrmarshall]

Adding a commit so I can test the labelling functionality

Description

Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution?

Manual testing steps

1. Step1: 2. Step2: 3. ....

Screenshots/Recordings

If applicable, add screenshots and/or recordings to visualize the before and after of your change.

Before

[screenshot]

After

[screenshot]

Related issues

Fixes #???

Pre-merge author checklist

• [ ] I’ve followed MetaMask Coding Standards.
• [ ] I've clearly explained:
  • [ ] What problem this PR is solving.
  • [ ] How this problem was solved.
  • [ ] How reviewers can test my changes.
• [ ] I’ve indicated what issue this PR is linked to: Fixes #???
• [ ] I’ve included tests if applicable.
• [ ] I’ve documented any added code.
• [ ] I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.
• [ ] I’ve properly set the pull request status:
  • [ ] In case it's not yet "ready for review", I've set it to "draft".
  • [ ] In case it's "ready for review", I've changed it from "draft" to "non-draft".

Pre-merge reviewer checklist

• [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.