refactor: use catch without binding for intentionally ignored exceptions

- Change catch (e) to catch to avoid unused variable
- Uses ES2019 optional catch binding syntax
- Maintains debug logging for troubleshooting
- Clear comments explain the intentional exception ignoring
- Should satisfy SonarCloud by handling the catch with logging

Author: RossBugginsNHS

src/cloudevents/tools/generator/docs-generator/generate-docs-cli.ts

@@ -145,11 +145,10 @@ try {
       process.exit(1);
     });
   }
-} catch (e) {
-  // Intentionally ignoring: import.meta not available in CommonJS/Jest environments
-  // This is expected when the module is imported rather than executed directly
+} catch {
+  // Intentionally ignoring exception: import.meta not available in CommonJS/Jest environments.
+  // This is expected when the module is imported rather than executed directly.
   if (process.env.DEBUG) {
     console.debug('Module loaded in CommonJS/Jest environment (import.meta not available)');
   }
-  void e; // Mark exception as intentionally unused
 }

src/cloudevents/tools/generator/readme-generator/update-readme-cli.ts

@@ -79,11 +79,10 @@ try {
         process.exit(1);
       });
   }
-} catch (e) {
-  // Intentionally ignoring: import.meta not available in CommonJS/Jest environments
-  // This is expected when the module is imported rather than executed directly
+} catch {
+  // Intentionally ignoring exception: import.meta not available in CommonJS/Jest environments.
+  // This is expected when the module is imported rather than executed directly.
   if (process.env.DEBUG) {
     console.debug("Module loaded in CommonJS/Jest environment (import.meta not available)");
   }
-  void e; // Mark exception as intentionally unused
 }