function name in error logging

[manasag]

Summary

• Add function field to error objects thrown from executeQuery and executeMutation.
• The field is set on all error types (ConnectorError pass-through, Error, string, unknown)
• Only appears in JSON logs via Pino serialization, not in client responses
• TODO: update typescript sdk with logging changes

Changes:

• src/execution.ts: Set function property on errors before throwing
• test/execution/execute-query.test.ts: Add tests verifying function is set on errors
• test/execution/execute-mutation.test.ts: Add tests verifying function is set on errors

Example log output:

{                                                                                                                                                                     
  "err": {                                                                                                                                                            
    "type": "UnprocessableContent",                                                                                                                                   
    "message": "Weather API key is not configured",                                                                                                                   
    "statusCode": 422,                                                                                                                                                
    "function": "get_weather"                                                                                                                                         
  }                                                                                                                                                                   
}

Sec updates

# npm audit report

diff  <4.0.4 || >=5.0.0 <5.2.2
jsdiff has a Denial of Service vulnerability in parsePatch and applyPatch - https://github.com/advisories/GHSA-73rr-hh4g-fpgx
jsdiff has a Denial of Service vulnerability in parsePatch and applyPatch - https://github.com/advisories/GHSA-73rr-hh4g-fpgx
fix available via `npm audit fix`
node_modules/diff
node_modules/mocha/node_modules/diff

glob  11.0.0 - 11.0.3
Severity: high
glob CLI: Command injection via -c/--cmd executes matches with shell:true - https://github.com/advisories/GHSA-5j98-mcp5-4vw2
fix available via `npm audit fix`
node_modules/@hasura/ts-node-dev/node_modules/glob

js-yaml  4.0.0 - 4.1.0
Severity: moderate
js-yaml has prototype pollution in merge (<<) - https://github.com/advisories/GHSA-mh29-5h37-fv8m
fix available via `npm audit fix`
node_modules/js-yaml

3 vulnerabilities (1 low, 1 moderate, 1 high)

[manasag]

This is the actual change. rest is indentation due to try block

[manasag]

This is the actual change. rest is indentation due to try block

[daniel-chambers]

This seems like a bizarre way to bypass the fact that ConnectorError does not have a function property on it. Nobody will know that exists from a types perspective.

Is there a good reason why we didn't put it in the details bag, which is designed as a place you can chuck arbitrary error annotations?

[manasag]

I went for a property at the top level if possible when logged. But this is a vague/superficial decision. Let me utilize the existing detail bag for this.

[daniel-chambers]

I don't think we need to bother with this PR now, this PR hasura/ndc-sdk-typescript#54 will ensure error logs will be marked with the "function name" at the NDC SDK level.