Fix errors when using the monorepo

[josephjclark]

Short Description

When the vm throws an error, we try and determine if that error comes from an adaptor. This makes assumptions about the callstack and the path of the file. It works fine for production adaptors, but when loading from the monorepo these tests fail.

Fixes #855

QA Notes

I am reproducing like this:

• In the monorepo, add this to common:

• Create a simple job which just calls tmp()
• From packages/cli, run pnpm openfn tmp/job.js -ma common (where tmp/job.js points to the simple job)
• Against production, the error contains no details. Here, you get output like:

[CLI] ♦ Versions:
         ▸ node.js                    22.12.0
         ▸ cli                        1.10.0
         ▸ @openfn/language-common    monorepo
[CLI] ✔ Loading adaptors from monorepo at /home/joe/repo/openfn/adaptors
[CLI] ⚠ Skipping auto-install as monorepo is being used
[CLI] ✔ Compiled all expressions in workflow
[R/T] ✘ job-1 aborted with error (100ms)

[R/T] ✘ Error reported by "tmp()" operation line 1:
[R/T] ✘ Error: TEST_ERROR: this is a test
[R/T] ✘ Additional error details:
{
  type: 'Error',
  message: 'TEST_ERROR: this is a test',
  code: 'TEST_ERROR',
  description: 'this is a test',
  jam: 'jar'
}

[R/T] ✘ Check state.errors.job-1 for details
[CLI] ✔ State written to tmp/errors/output.json
[CLI] ⚠ Errors reported in 1 jobs
[CLI] ✔ Finished in 152ms

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

You can read more details in our Responsible AI Policy

[josephjclark]

This is a bit hairy

We're looking in the callstack or a path like adaptors/packages/common/dist

Because the path to an adaptor in the monorepo isn't terribly distinctive. path likepackages/*/dist feels like it might erroneously match against many paths (then again maybe not? Most node_modules code would be like packagename/dist, with nothing in between.

Anyway, because of this, I wanted to put the repo name in the path.

But that doesn't work for anyone who forks the repo with a different name locally. In those cases, the path won't match and bad errors will be triggered, which leads to misleading error reports when developing adaptors.

Perhaps I can do a regex like "not node_modules and packages/./dist"

[josephjclark]

Ah it's fine - I'm sure packages/./dist is all we need for this. There's only a small amount of non-vm error cases that we need to handle. Let's try it out.