JSDOM returns an error if there is almost no rules to run

[sarvaje]

If we deactivate all or almost all the rules and the option for the collector 'waitFor' is low, then we receive an error running sonar.

Steps to reproduce:

1. use this configuration

   {
       "collector": {
           "name": "jsdom",
           "options": {
               "waitFor": 100
           }
       },
       "formatter": "stylish",
       "rules": {
           "axe": "off",
           "disallowed-headers": "off",
           "disown-opener": "off",
           "manifest-exists": "off",
           "manifest-file-extension": "off",
           "manifest-is-valid": "off",
           "no-friendly-error-pages": "off",
           "no-html-only-headers": "off",
           "no-protocol-relative-urls": "off",
           "ssllabs": "off",
           "x-content-type-options": "warning"
       }
   }
   

2. run sonar npm run site -- https://developer.microsoft.com/en-us/microsoft-edge/

Expected:
Sonar report some warnings with x-content-type-options and returns with status code 0

Actual
Sonar report some errors with x-content-type-options and throw an expection:

[molant]

From what I see this seems to happen because there are pending requests, we are calling .close() and the request manager crashes.
Because we are ending everything I think it should be enough with having a try/catch in the .close() method. At this point of the execution we don't care what happens to the collector next.