Fix the 'no terminal detected' error flood

A small number of users are hitting this issue, and sending error reports
every 10 seconds while the app is open. This is annoying.

For now, I've disabled the existing Sentry DSN. This commit moves to a
new one (for the exact same project), and ensures that reports are
only ever sent once.

Author: pimterry

src/error-tracking.ts

@@ -9,7 +9,7 @@ export function initErrorTracking() {
     let { SENTRY_DSN } = process.env;
     if (!SENTRY_DSN && IS_PROD_BUILD) {
         // If we're a built binary, use the standard DSN automatically
-        SENTRY_DSN = 'https://f6775276f60042bea6d5e951ca1d0e91@sentry.io/1371158';
+        SENTRY_DSN = 'https://5838a5520ad44602ae46793727e49ef5@sentry.io/1371158';
     }
 
     if (SENTRY_DSN) {

src/interceptors/terminal/fresh-terminal-interceptor.ts

@@ -360,6 +360,11 @@ const resetShellStartupScripts = () => {
 
 const terminals: _.Dictionary<ChildProcess[] | undefined> = {}
 
+// Memoize this report: i.e. send it only once
+const reportNoTerminal = _.memoize(() => {
+    reportError('No terminal could be detected');
+});
+
 export class TerminalInterceptor implements Interceptor {
 
     id = 'fresh-terminal';
@@ -369,7 +374,7 @@ export class TerminalInterceptor implements Interceptor {
 
     async isActivable(): Promise<boolean> {
         const terminalAvailable = !!(await getTerminalCommand());
-        if (!terminalAvailable) reportError('No terminal could be detected');
+        if (!terminalAvailable) reportNoTerminal();
         return terminalAvailable;
     }