fix: set context as metadata in bugsnag error notification

[saikumarrs]

Description of the change

Bugsnag groups errors based on the context and error message. It assumes a default context based on the code region where the error originated. Previously, we've been setting the context explicitly.
As a result, if the same type of error (a type error during destination transformation) occurs for multiple destinations, Bugsnag groups them together. Therefore, the notification rules and thresholds are applied as a whole group resulting in fewer alerts by shadowing other destination alerts.

Hence, the contextual information, such as (Router Transformation, Processor Transformation, etc.) is now moved to the metadata.

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Related issues

N/A

Checklists

Development

• Lint rules pass locally
• The code changed/added as part of this pull request has been covered with tests
• All tests related to the changed code pass in development

Code review

• This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
• "Ready for review" label attached to the PR and reviewers mentioned in a comment
• Changes have been reviewed by at least one other engineer
• Issue from task tracker has a link to this pull request