Update $convert-data error log

[pallar-ms]

Description

Update $convert-data error log. Currently, the entire exception is logged in some cases (except post processing exceptions) which might not be ideal in case the message has text from the input data being processed. Updating the log to only mention exception type, FHIRConverterErrorCode and stack trace.

Related issues

Addresses AB#120207.

Testing

Describe how this change was tested.

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 65 characters
• Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
• Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
• Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
• Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
• [ ] CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

[pallar-ms]

@LTA-Thinking , thanks for taking a look. Question - the PR build & deploy seems to be failing at an unrelated change to this PR, and I am also seeing other PRs blocked by the same error. Do you know if anyone is taking a look into that? What is the best place to bring this up and track status?