chore: add stack and cause to trpc error logging

[Meierschlumpf]

Homarr

Thank you for your contribution. Please ensure that your pull request meets the following pull request:

• Builds without warnings or errors (pnpm buid, autofix with pnpm format:fix)
• Pull request targets dev branch
• Commits follow the conventional commits guideline
• No shorthand variable names are used (eg. x, y, i or any abbrevation)

I'll suggest that we add this as it allows more informative log messages that also allow us to know why the fetch failed for example #2017

[deepsource-io]

Here's the code health analysis summary for commits 55feb9d..c3b5376. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	21.05%	8268 / 39269
🔵	Statements	21.05%	8268 / 39269
🔵	Functions	25.12%	306 / 1218
🔵	Branches	61.76%	908 / 1470

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
apps/nextjs/src/app/api/trpc/[trpc]/route.ts	0%	0%	0%	0%	1-43

Generated in workflow #4692 for commit c3b5376 by the Vitest Coverage Report Action