Fix DataClone Errors

[josephjclark]

Short Description

This PR fixes an issue where exceptions thrown by Adaptors can include unserializable data (I'm looking at you, Axios), triggering a crash in the worker.

Fixes #871

Implementation Details

This is one of those that takes 2 days of head scratching and then a single line code diff.

This is the second fix and there are two things to note:

1. The test to determine whether an error is an AdaptorError was too strict. This meant that in some cases (depending on what state the repo happens to be in) the runtime was wrongly deciding errors weren't from the adaptor. The upshot of this is that sometimes the DataCL=loneError does not occur (it did not occur locally or on staging while I was debugging).
2. When an adaptorerror is created, we now force a call to fast-safe-stringify to ensure that it serializes safely. This prevents the data clone error occurring downstream.

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to know!):

• Code generation (copilot but not intellisense)
• Learning or fact checking
• Strategy / design
• Optimisation / refactoring
• Translation / spellchecking / doc gen
• Other
• I have not used AI