fix(pouchdb-errors): guard Error.stack access when stack is inaccessible

[Mayankaggarwal8055]

This PR makes the error handling in pouchdb-errors more robust.

In some environments, accessing Error.stack can throw an exception. The previous implementation assumed that the stack property would always be accessible, which could cause the error handling itself to crash.

This change wraps the stack assignment in a try/catch block and provides a safe fallback when the stack cannot be accessed. This ensures that error objects are still created properly even in restricted environments.

Fixes #9067

[Mayankaggarwal8055]

The current codebase does not define CustomPouchError, so only the stack-safety change from the reported patch was applicable.

[Mayankaggarwal8055]

Hey @janl , could you please take a look at this when you get a moment?

I’ve implemented the fix for handling Error.stack safely by wrapping it in a try/catch to avoid crashes in restricted environments. The change is minimal and keeps the existing behavior intact while making it more robust.

Everything is working fine locally, and the fix directly addresses the issue discussed. Would really appreciate your feedback or any suggestions for improvement.

Thanks! 🙌

Requested changes now applied

[SourceR85]

Should be fine.
Someone else needs to review, since I was involved too much and did 3 things at the time during this review/refinement.

[janl]

can you please reinstate our PR template and fill it out accordingly?