mssql Improve error logs

[mtuchi]

Summary

Fix typo in changelog and log entire error message

Details

When the job fail on lightning the logs does not contain any useful information that could help with debugging, See example error message 👇🏽

T Failed step Upsert feedback table on Azure after 2.348s
R/T {
  "details": {},
  "message": "",
  "name": "AdaptorError",
  "severity": "fail",
  "source": "runtime"
}
R/T Check state.errors.b1de9d3b-ba65-49cf-8fff-147759b09736 for details.
R/T Run complete with status: fail
AdaptorError: unknown

This PR makes sure we log the whole error message when we have an error

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

Review Checklist

Before merging, the reviewer should check the following items:

• Does the PR do what it claims to do?
• If this is a new adaptor, added the adaptor on marketing website ?
• Are there any unit tests?
• Is there a changeset associated with this PR? Should there be? Note that
  dev only changes don't need a changeset.
• Have you ticked a box under AI Usage?

[josephjclark]

@mtuchi Does this actually fix the issue - do you get a better error report out?

If so you can bump versions and merge

[mtuchi]

@josephjclark yes i have a better error report now