Update error handling

[reecebrowne]

Description of Changes

<-- Updated tool error handling to better handle errors instead of suppressing most Closes #(issue_number) -->

---

Checklist

General

• [ ] I have read the Contribution Guidelines
• [ ] I have read the Stirling-PDF Developer Guide (if applicable)
• [ ] I have read the How to add new languages to Stirling-PDF (if applicable)
• [ ] I have performed a self-review of my own code
• [ ] My changes generate no new warnings

Documentation

• [ ] I have updated relevant docs on Stirling-PDF's doc repo (if functionality has heavily changed)
• [ ] I have read the section Add New Translation Tags (for new translation tags only)

UI Changes (if applicable)

• [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR)

Testing (if applicable)

• [ ] I have tested my changes locally. Refer to the Testing Guide for more details.

[stirlingbot[bot]]

✅ Frontend License Check Passed

All frontend licenses have been validated and no compatibility warnings were detected.

The frontend license report has been updated successfully.

[stirlingbot[bot]]

🚀 V2 Auto-Deployment Complete!

Your V2 PR with the new frontend/backend split architecture has been deployed!

🔗 Direct Test URL (non-SSL) http://185.252.234.121:4208

🔐 Secure HTTPS URL: https://4208.ssl.stirlingpdf.cloud

This deployment will be automatically cleaned up when the PR is closed.

🔄 Auto-deployed because PR title or branch name contains V2/version2/React keywords.