Control + C Fails to cleanly stop sherlock #2756

[MeriemBchini]

Fix: Clean Ctrl+C handling and immediate exit

Problem

Sherlock did not handle Ctrl+C (SIGINT) cleanly in all cases.
Interrupting execution could leave the program in an inconsistent state or delay termination due to ongoing requests.

Solution

• Implemented a proper signal handler for SIGINT
• Ensured the program exits immediately and gracefully when Ctrl+C is triggered
• Prevented unnecessary stack traces or hanging behavior during interruption

Changes

• Added/updated handler() for clean exit
• Integrated signal handling into the main execution flow
• Improved user experience during long-running scans

Result

• Immediate and clean termination on Ctrl+C
• No unexpected errors or delays when stopping execution
• Improved CLI usability

Notes

• No impact on existing features or output formats
• Backward compatible with current behavior