Log 500's to Request Metric

[apurvabhaleMS]

Description

When any unknown/unhandled error occurs, the context get's updated after the ApiResponseNotification is published. Due to this 500s or any unknown/unhandled errors are not getting logged in RequestMetric.

Related issues

Addresses 81035.

Testing

Test if 500s are getting logged in RequestMetric table

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 50 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, Dependencies, Enhancement, or New-Feature
• Tag the PR with Azure API for FHIR if this will release to the Azure API for FHIR managed service (CosmosDB or common code related to service)
• Tag the PR with Azure Healthcare APIs if this will release to the Azure Healthcare APIs managed service (Sql server or common code related to service)
• Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

[apurvabhaleMS]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[apurvabhaleMS]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).