[EPIC] SEP #5 - Update header/widget

[iamacook]

What it solves

Resolves missing type/staging URL for SEP #5 claiming data

How this PR fixes it

The forthcoming claiming data for SEP #5 will be tagged under user_v2. This adds the new type, as well as the staging URL.

How to test it

Open the PR deployment on a Safe that is part of the test allocation and observe the increased allocation in the header/governance app widget.

Checklist

• I've tested the branch on mobile 📱
• I've documented how it affects the analytics (if at all) 📊
• I've written a unit/e2e test for it (if applicable) 🧑‍💻

[github-actions]

Branch preview

✅ Deploy successful!

https://sep5_type--walletweb.review-wallet-web.5afe.dev

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	0	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	0	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[liliya-soroka]

incorrect amount in displayed
- https://sep5_type--walletweb.review-wallet-web.5afe.dev/home?safe=gor:0xC642bEc0e4f69815e89723C09caA8DAa524cAc9c

Same in my safe on prod without SEP5 allocation
- https://app.safe.global/home?safe=gor:0xC642bEc0e4f69815e89723C09caA8DAa524cAc9c

Please, check that the test data is correct

[iamacook]

incorrect amount in displayed - https://sep5_type--walletweb.review-wallet-web.5afe.dev/home?safe=gor:0xC642bEc0e4f69815e89723C09caA8DAa524cAc9c

Same in my safe on prod without SEP5 allocation - https://app.safe.global/home?safe=gor:0xC642bEc0e4f69815e89723C09caA8DAa524cAc9c

Please, check that the test data is correct

There was an issue with the test data which has now been fixed. I can see the difference with the following Safe: gor:0xAecDFD3A19f777F0c03e6bf99AAfB59937d6467b.

[liliya-soroka]

Verified