Add stop at first match for interactsh matchers

[parrasajad]

Proposed changes

Extend stop at first match support to interactsh matchers

Example template (from issue)

id: test-interactsh

info:
  name: interactsh test
  author: pdteam
  severity: info

requests:
  - raw:
      - |
        GET /api/geoping/{{interactsh-url}} HTTP/1.1
        Host: {{Hostname}}

      - |
        GET /api/geoping/{{interactsh-url}} HTTP/1.1
        Host: {{Hostname}}

    stop-at-first-match: true
    matchers:
      - type: word
        part: interactsh_protocol  # Confirms the DNS Interaction
        words:
          - "dns"

echo https://geonet.shodan.io | nuclei -t test.yaml 

[test-interactsh] [http] [info] https://geonet.shodan.io/api/geoping/c70q752ciaeivnpbsr1gc8y48cyyyyyyr.interact.sh

Checklist

• Pull request is created against the dev branch
• All checks passed (lint, unit/integration/regression tests etc.) with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[ehsandeep]

Unrelated to this PR, there is a whois test failing on macos - https://github.com/projectdiscovery/nuclei/runs/4593459674?check_suite_focus=true

[Ice3man543]

@parrasajad instead of having a global c.matched value and tracking it for ignoring further interact event, I guess what we should do here is to prevent duplicated interactsh matches from same template if we have stop at first match attribute. If we apply this globally, no interactions will match even for other templates since the interactsh client is shared.

We can implement some sort of tracking logic in protocols/common/interactsh for this.

[Ice3man543]

lgtm!