fix: improve mobile token error logging

[reidzeibel]

Ref: Slack thread

Also maybe part of https://github.com/AtB-AS/kundevendt/issues/20215

Thomas from Entur notified us that our logging leaves many details out, so he asked if there are possibilities to improve it.

This PR will update the breadcrumb logging as shown below, hopefully will expose the metadata part more, and shows the stack if any.

from

  error: (msg, err, metadata?) => {
    logToBugsnag('Mobiletoken sdk info message: ' + msg, metadata);
    const onError = toOnErrorCallback('warning', msg, metadata);
    if (err) notifyBugsnag(err, {errorGroupHash: 'token', metadata: onError});
  }

to

  error: (msg, err, metadata?) => {
    logToBugsnag(`Mobiletoken sdk error message: ${msg} ${err}`, {
      'name': metadata?.name,
      'message' : metadata?.message,
      'stack' : metadata?.stack
    });
    const onError = toOnErrorCallback('error', msg, metadata);
    if (err) notifyBugsnag(err, {errorGroupHash: 'token', metadata: onError});
  }

Acceptance criteria

• Error message on Bugsnag now shows the metadata properly (may need to be tested in prod?)

[tormoseng]

✅ Tested OK. See this event.

@reidzeibel When looking at the event. Do you think you'll get more info from the breadcrumb stacktrace than the event stacktrace? Just a question to possibly limit the amount of data from the user. If it's valuable, let's go!

[tormoseng]

By the way, I cannot see a large difference from "normal" Bugsnag events in terms of size. So, let's go!

[reidzeibel]

@tormoseng We'll need to see on Android, since the stacktrace on iOS is kind of broken now. Then we can compare the event stacktrace vs breadcrumb stacktrace and see what we should do next.

[tormoseng]

@reidzeibel Here is a bugsnag event for Android: ref

[reidzeibel]

@tormoseng seems like the breadcrumbs stacktrace gives more information here 🤔 , can we even skip the event stacktrace?

[tormoseng]

Not sure. But it's not a way more data sent, so let's just keep it as is.