bug: sentry reports for script errors go to bloom instead of keyman instance

[mcdurdin]

The Sentry setup on sentry.io for keyman.com gives the following snippet for us to integrate:

<script
  src="https://js.sentry-cdn.com/bba22972ad6b4c2ab03a056f549cc23d.min.js"
  crossorigin="anonymous"
></script>

And ... we have Bloom's project ID there for keyman.com, rather than ours -- when we setup we forgot to click the tiny little arrow to swap to the correct project.

This causes script parse errors to be reported via Sentry's final fallback error handler to go to Bloom's sentry instance instead of the appropriate Keyman one.

This needs to be fixed on all websites, in KeymanSentry.php, static function GetBrowserHtml($dsn, $release = null) {.

Reported by @andrew-polk