[build-info] Bugsnag error formatting is incorrect and noisy

[jackbrewer]

Describe the bug

We're getting a lot of reports in the Netlify Bugsnag account, going through metrics.ts. Whilst they may all be actual errors, the way they are being reported is making the Bugsnag flow awkward as they all appear as misconfigured. Also they clump together meaning we can't ignore expected vs unexpected reports.

We are currently seeing ~80,000 reports of this every 30 days 🙃

The first instance seems to be around 5 July at 7:26:22 UTC (from Slack logs), which is close to the time we started using 7.3.3 in the React App (although there were many releases in a short time around this point).

Steps to reproduce

Not sure how to trigger each report type (or if we need to), but to see the reports, search status:open build-info/lib/metrics.js:6 in the Bugsnag timeline view.

Configuration

No response

Deploy logs

n/a

[benedfit]

It would appear that when an object is passed to Bugsnag.notify() is needs to be an Error in order to stop this message from being logged:

bugsnag/bugsnag-js#1713 (comment)