Bypass403 Failure Threshold

[TheTechromancer]

When bypass403 encounters a downed/slow web server, it can spend a very long time (10+ minutes) on a single host:

2024-02-06 18:57:50,249 [INFO] bbot.scanner scanner.py:900 hideous_howard: No events in queue
2024-02-06 18:58:05,251 [INFO] bbot.scanner scanner.py:900 hideous_howard: Modules running (incoming:processing:outgoing) bypass403(374:1:0)
2024-02-06 18:58:05,252 [INFO] bbot.scanner scanner.py:900 hideous_howard: Events produced so far: DNS_NAME: 2500, OPEN_TCP_PORT: 792, URL: 619, PROTOCOL: 606, WAF: 541, FINDING: 416, TECHNOLOGY: 172, IP_ADDRESS: 168, ASN: 165, VULNERABILITY: 115, EMAIL_ADDRESS: 46, SCAN: 1, ORG_STUB: 1
...
2024-02-06 19:21:20,626 [INFO] bbot.scanner scanner.py:900 hideous_howard: No events in queue
2024-02-06 19:21:35,629 [INFO] bbot.scanner scanner.py:900 hideous_howard: Modules running (incoming:processing:outgoing) bypass403(374:1:0)
2024-02-06 19:21:35,630 [INFO] bbot.scanner scanner.py:900 hideous_howard: Events produced so far: DNS_NAME: 2500, OPEN_TCP_PORT: 792, URL: 619, PROTOCOL: 606, WAF: 541, FINDING: 416, TECHNOLOGY: 172, IP_ADDRESS
: 168, ASN: 165, VULNERABILITY: 115, EMAIL_ADDRESS: 46, SCAN: 1, ORG_STUB: 1

When looping through signatures, we should abort if too many requests have failed.

[liquidsec]

added in #1070