Don't report ENOENT trying to delete config files

This is caused by a race, but it's harmless and fastest to just let it
happen. The end result is exactly what we want (the file is gone), so we
just ignore it.

Author: pimterry

src/browsers.ts

@@ -43,6 +43,10 @@ export async function checkBrowserConfig(configPath: string) {
 
         console.warn('Failed to read browser config on startup', error);
         return deleteFile(browserConfig).catch((err) => {
+            // We can have a race if the file was invalid AND old, which case we can get a parse error
+            // and have deleted the file already. Regardless: it's now gone, so we're all good.
+            if (err.code === 'ENOENT') return;
+
             console.error('Failed to clear broken config file:', err);
             reportError(err);
         });