Chore: prod build on staging (main)

[katspaugh]

What it solves

In order to be able to test our app with production settings before a release, we'll be building and deploying a production version on staging from the main branch.

With this setup, https://safe-wallet-web.staging.5afe.dev can be used as a close-to-prod environment for pre-release testing.

[github-actions]

Branch preview

✅ Deploy successful!

https://prod_build--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]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	75.05%	10108/13469
🔴	Branches	49.59%	2055/4144
🔴	Functions	57.46%	1498/2607
🟡	Lines	76.62%	9144/11934

Test suite run success

1105 tests passing in 155 suites.

Report generated by 🧪jest coverage report action from 83f5b73

[francovenica]

The only issue I had in this environment is that I cannot use social login because of an authorization error. I don't have this issue in the current staging env.

I'm not sure if this is because of this being a PR environment, or if if has to do with the setup done in this PR.
If it is the former, then I'm ok with approving this ticket

[katspaugh]

@schmanu we need to whitelist the domain right?

[usame-algan]

Yes this PR deployment is not whitelisted but since the branch name contains a - Google doesn't allow it to be whitelisted.

[katspaugh]

https://safe-wallet-web.staging.5afe.dev/ needs to be white-listed, not this branch.