chore: Update nextjs to v13.5

[usame-algan]

What it solves

• Update next to v13.5
• Resolves broken imports as a result of the update
• Replaces optimizeImports with experimental optimizePackageImports that doesn't require explicit mappings

How to test it

• Navigating the app still works

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://update_next--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}

[francovenica]

Looks good to me

I've just did a quick smoke through the site and everything worked fine
I've checked a share link in the safe apps Usame told me I should give a try.

[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}

[usame-algan]

Looks like this update causes issues with our patch for the next-pwa package. Updating the next-pwa package to v9.7.1 fixes it but breaks our patch. Updating the patch doesn't work anymore either so our service worker doesn't work. We will have to look further into this cc @iamacook

[katspaugh]

Service workers seem to be fine w/o the patch.