chore: improve lint setup (#397)

- update eslint config to closely mirror the ones from ferdium-app
- add .eslintignore
- opt in to eslint `reportUnusedDisableDirectives` config option
- remove `trailingComma: all` from `prettier` config which is default in `prettier` v3
- autofix or disable a lot of lint issues throughout codebase
- add `volta` configuration to `package.json` to autoload correct `node` and `pnpm` versions
- upgrade all `eslint` and `prettier` related dependencies to latest
- update lint:fix npm script
- reformat touched files with prettier
- bumped up minor version for all recipes that have changes
- introduced injection of 'service.css' where it was missing in many recipes

---------

Co-authored-by: Vijay A <vraravam@users.noreply.github.com>

1 files changed, 20 insertions, 17 deletions

diff --git a/recipes/msteams/index.js b/recipes/msteams/index.js
index c8cdc38..ea86196 100644
--- a/recipes/msteams/index.js
+++ b/recipes/msteams/index.js
@@ -1,18 +1,21 @@
-module.exports = Ferdium => class MicrosoftTeams extends Ferdium {
-  overrideUserAgent() {
-    return window.navigator.userAgent.replace(/(Ferdium|Electron)\/\S+ \([^)]+\)/g, '').trim();
-  }
+module.exports = Ferdium =>
+  class MicrosoftTeams extends Ferdium {
+    overrideUserAgent() {
+      return window.navigator.userAgent
+        .replaceAll(/(Ferdium|Electron)\/\S+ \([^)]+\)/g, '')
+        .trim();
+    }
 
-  // TODO: Commenting out since this can expose the user to a MITM attack. Before this can be turned on, we will need to put in some safeguards/warnings that the user can explicitly accept the security ramifications
-  // // https://docs.microsoft.com/en-us/microsoftteams/troubleshoot/teams-sign-in/sign-in-loop#resolution
-  // knownCertificateHosts() {
-  //   return [
-  //     'microsoft.com',
-  //     'microsoftonline.com',
-  //     'teams.skype.com',
-  //     'teams.microsoft.com',
-  //     'sfbassets.com',
-  //     'skypeforbusiness.com',
-  //   ];
-  // };
-};
+    // TODO: Commenting out since this can expose the user to a MITM attack. Before this can be turned on, we will need to put in some safeguards/warnings that the user can explicitly accept the security ramifications
+    // // https://docs.microsoft.com/en-us/microsoftteams/troubleshoot/teams-sign-in/sign-in-loop#resolution
+    // knownCertificateHosts() {
+    //   return [
+    //     'microsoft.com',
+    //     'microsoftonline.com',
+    //     'teams.skype.com',
+    //     'teams.microsoft.com',
+    //     'sfbassets.com',
+    //     'skypeforbusiness.com',
+    //   ];
+    // };
+  };