[FEAT] Adds better logging for render errors

[pzuraq]

[rwjblue]

Chatted with @pzuraq offline, we should migrate this away from try/catch back to using try/finally. As a try/catch we somewhat fundamentally break developer ergonomics (when using "break on uncaught exceptions" it should stop in userland helper code, not our own internals).

The original need that caused this to be moved to try/catch was the deopts that were being triggered in that code that should only be ran when there is an actual exception. We can avoid that same issue by doing something akin to this instead:

let didError = true;
try {
  doSomething();
  didError = false;
} finally {
  if (didError) {
    console.log('error yo!')
  }
}

Doing this avoids the dev ergonomics issues and the deopt that was the original reason for moving to try/catch.

---

In this context, I think we should change this PR from assigning e.message to directly console.log'ing instead.

[rwjblue]

For those that are curious, here is a smallish codepen that demos the dev ergonomics issue I was referring to: https://codepen.io/rwjblue/full/PozYKqw.

When you run it, make sure to have DevTools open and "Pause on uncaught exceptions" set in the sources tab. The execution should pause in the someBadFunction implementation where throw new Error() is called, but it is actually pausing inside the catch block where we throw e.

[rwjblue]

#1172 addresses the removal of try/catch here, this will need a rebase after that lands

[rwjblue]

kk, ready for a rebase / rework now @pzuraq