lint: Add linter rule to ban unexplained console.error calls

[plibither8]

This PR is partially completes https://github.com/sourcegraph/sourcegraph/issues/26582. Next step would be to create a PR in the sourcegraph repo to console.error errors captured by Sentry.

---

This rule bans logging errors directly to the console using console.error() calls, unless supported with a comment explaining why it's required. Otherwise, it's recommended to pass the error through Sentry.captureException().

Bad code

try {
  // do something
} catch (error) {
  console.error(error)
}

Okay code

try {
  // do something
} catch (error) {
  // We need to log this to the browser console because XYZ
  console.error(error)
}

(Bonus) Awesome code

try {
  // do something
} catch (error) {
  Sentry.captureException(error)
}

[valerybugakov]

Looks great! Let's decide on the error message, and it's good to go 🙌

[valerybugakov]

Depending on the outcome of the discussion in the follow-up PR, we would need to update the message here. Using Sentry.captureException directly is not safe because it's not always available. We would want to point consumers to something more generic that encapsulates Sentry and other output channels.