fix: errors thrown in functions over the contextBridge

[codebytere]

Description of Change

Closes #28327.

Fixes an issue where errors thrown in functions passed over the contextBridge would be prefixed with Uncaught Error so that the error message then incorrectly displayed as Error: Uncaught Error: test. This is owed to the fact that errors aren't serializable as-is, so we should be pulling the message off the exception and re-constructing and throwing it in the destination context

Tested with https://gist.github.com/f11c77f9bc2cbf98d42a9fcaf477c80a.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Fixed an issue where errors thrown in functions passed over the contextBridge could be displayed incorrectly.

[release-clerk]

Release Notes Persisted

Fixed an issue where errors thrown in functions passed over the contextBridge could be displayed incorrectly.

[trop]

I was unable to backport this PR to "11-x-y" cleanly;
you will need to perform this backport manually.

[trop]

I was unable to backport this PR to "12-x-y" cleanly;
you will need to perform this backport manually.

[trop]

I was unable to backport this PR to "13-x-y" cleanly;
you will need to perform this backport manually.

[trop]

@codebytere has manually backported this PR to "13-x-y", please check out #28446

[trop]

@codebytere has manually backported this PR to "12-x-y", please check out #28447