🔧 Fix error handling for better ESLint compatibility

Rename caught error variables to follow ESLint naming convention

Update error handling across plugins to use _err pattern for unused
caught errors, avoiding ESLint warnings. Add corresponding rule
to eslint.config.mjs with caughtErrorsIgnorePattern to standardize
this approach project-wide.

This change maintains all error handling functionality while making
the codebase more consistent with our linting standards.

Author: hyperb1iss

eslint.config.mjs

@@ -45,6 +45,7 @@ const eslintConfig = [
         {
           argsIgnorePattern: "^_",
           varsIgnorePattern: "^h$",
+          caughtErrorsIgnorePattern: "^_"
         },
       ],
     },

plugins/decorators.ts

@@ -60,7 +60,7 @@ const EFFECT_METADATA_SYMBOL = Symbol.for('lightscript:effect');
               // Quietly reload without noisy output
               server.ws.send({ type: "full-reload" });
             }
-          } catch (err) {
+          } catch (_err) {
             console.error(`[✗] Error processing file ${path}`);
           }
         }

plugins/signalrgb.ts

@@ -103,7 +103,7 @@ function extractAllDecorators(
         property: propertyName,
         options: options,
       });
-    } catch (err) {
+    } catch (_err) {
       logger.error(`Error parsing ${decoratorName} decorator`);
     }
   }
@@ -301,7 +301,7 @@ function processEffect(effect: (typeof effects)[0]) {
           }
         }
       }
-    } catch (err) {
+    } catch (_err) {
       logger.error(`Error extracting metadata for ${effect.id}`);
     }
 
@@ -334,7 +334,7 @@ function processEffect(effect: (typeof effects)[0]) {
     );
 
     logger.effect(effect.id, "HTML file created successfully");
-  } catch (err) {
+  } catch (_err) {
     logger.error(`Error processing effect ${effect.id}`);
   }
 }