chore: Replace honeybadger-js with honeybadger-io/js

[abshierjoel]

Part of #1980

This is based on honeybadger's migration guide here: https://docs.honeybadger.io/lib/javascript/support/upgrading-to-v3/

Checklist

Authors and Reviewer(s), please verify the following:

• A PR description, regardless of the triviality of this change, that communicates the value of this PR
• Well-formatted conventional commit messages that provide context into the change
• Documentation updated or issue created (provide link to issue/PR)
• Signed CLA (if not already signed)
• Feature flagged, if applicable

[hansenreid]

@wdoconnell can you take a look at this?

[wdoconnell]

Taking a look now 👍

[wdoconnell]

This generally looks correct but I need to spend a little more time with it - the case that applies to us is somewhat different from the guide in that we're going from 1.x of the client-side package (instructions are for 2.x of client side package or 1.x of node package).

[wdoconnell]

Finished reviewing - this looks correct. The guide isn't specific to honeybadger-v1.x upgrades but for our purposes the changes required look to be the same.

Only other thing I'd note from the upgrade instructions:
Previously deprecated snake case config options such as api_key, project_root, etc. are no longer supported. Use apiKey, projectRoot instead.

Importantly, this only affects the config options themselves. The arguments passed to the honeybadger v1 api (see scripts/upload_sourcemap.sh) are unchanged, so "api_key" is there still "api_key" rather than apiKey.

I'll monitor this after it merges to make sure we don't lose honeybadger reporting.