fix(utils): extract provider error fields from response data directly

[hassan254-prog]

Describe the problem and your solution

• Widen this to extract provider error fields directly from the response data instead of reading them from the error object.

---

Adjust provider error extraction from response.data in stringifyError

Updates stringifyError to extract whitelisted provider error fields directly from response.data rather than only from a nested response.data.error object, skipping object values to avoid nested payloads. Tests in packages/utils/lib/errors.unit.test.ts are revised and expanded to cover top-level field extraction, invalid structures, and priority over Boom payloads.

---

This summary was automatically generated by @propel-code-bot

[propel-code-bot]

No issues found; changes appear correct and tests cover expected behavior.

Status: No Issues Found | Risk: Low

Review Details

📁 2 files reviewed | 💬 0 comments

Instruction Files

├── .claude/
│   ├── agents/
│   │   └── nango-docs-migrator.md
│   └── skills/
│       ├── agent-builder-skill/
│       │   ├── EXAMPLES.md
│       │   └── SKILL.md
│       ├── creating-integration-docs/
│       │   └── SKILL.md
│       └── creating-skills-skill/
│           └── SKILL.md
├── AGENTS.md
└── GEMINI.md

[TBonnin]

we are changing the semantic of the logic, not looking at responseData.error anymore but responseData. Anything in .error will be skipped since in the line below object value are filtered out.
Are we not breaking current behavior?

[TBonnin]

why value === null?

[linear]

NAN-4882 Build out unit test suite for different provider errors