fix(accessibility): preserve build-start exception log on glob.sync failure (SDK-7121)

Addresses PR #1160 review r3682515873: switching the support-file glob to
glob.sync dropped the distinctive 'EXCEPTION IN BUILD START EVENT' log that
the removed async callback emitted on a parse error. Wrap glob.sync in its
own try/catch to restore that signal (now with the error object attached)
while keeping the call synchronous to avoid the archive race.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: osho-20

bin/accessibility-automation/helper.js

@@ -381,7 +381,13 @@ exports.setAccessibilityEventListeners = (bsConfig) => {
     // Synchronous for the same reason as testObservability setEventListeners
     // (SDK-7121): the caller archives the suite right after this returns, so an
     // async glob callback would race the archive and ship un-instrumented specs.
-    const files = glob.sync(globPattern, {});
+    let files;
+    try {
+      files = glob.sync(globPattern, {});
+    } catch(err) {
+      logger.debug('EXCEPTION IN BUILD START EVENT : Unable to parse cypress support files', true, err);
+      return;
+    }
     files.forEach(file => {
       try {
         const fileName = path.basename(file);