Adding Screenshot support

[Mzack9999]

Description

This PR adds basic support for headless mode by adding two new flags:

• -screenshot enables headless mode to take screenshots
• -system-chrome uses the local installed chrome if any

When the screenshot flag is used, also the rendered dom is retrieved and added to the json output under headless_body. The screenshot image is saved in the store response folder and an index file called index_screenshot.txt is created.

Doc - https://github.com/projectdiscovery/httpx/tree/issue-385-screenshot#screenshot

$ git clone https://github.com/projectdiscovery/httpx.git; cd httpx/cmd/httpx/
$ git checkout issue-385-screenshot
$ go build
$ echo www.projectdiscovery.io | ./httpx -screenshot
    __    __  __       _  __
   / /_  / /_/ /_____ | |/ /
  / __ \/ __/ __/ __ \|   /
 / / / / /_/ /_/ /_/ /   |
/_/ /_/\__/\__/ .___/_/|_|
             /_/

		projectdiscovery.io

[INF] Current httpx version v1.2.9 (latest)
https://www.projectdiscovery.io

tree output/
output/
├── response
│   ├── index.txt
│   └── www.projectdiscovery.io
│       └── 89dbec3c06cdc2f6e4586907775aecb0e2520783.txt
└── screenshot
    ├── index_screenshot.txt
    └── www.projectdiscovery.io
        └── 89dbec3c06cdc2f6e4586907775aecb0e2520783.png

6 directories, 4 files

[Mzack9999]

Todo:

• Hanging zombie chromium processes on windows
• save screenshots in $output/screenshots
• Use absolute path for json fields referencing files

[Mzack9999]

• Leakless is blocked as malicious by windows defender

[Mzack9999]

Depends on projectdiscovery/utils#137

[tarunKoyalwar]

lgtm !

Q: when using -screenshot httpx stores response dump to responses even if -store-response is not used . Is this expected ?

[Mzack9999]

@tarunKoyalwar yeah I thought it could make sense to also store the response, as while taking screenshot we also retrieve the rendered DOM. What do you think @ehsandeep should we keep things separated?

[ehsandeep]

@tarunKoyalwar yeah I thought it could make sense to also store the response, as while taking screenshot we also retrieve the rendered DOM. What do you think @ehsandeep should we keep things separated?

we can keep the current behavior as it is since the response information can be used to associate with the screenshot information.

[ulises2k]

BUG: