Adding support for source/origin wappalyzer

[Mzack9999]

$ katana -json -u http://hackerone.com

   __        __
  / /_____ _/ /____ ____  ___ _
 /  '_/ _  / __/ _  / _ \/ _  /
/_/\_\\_,_/\__/\_,_/_//_/\_,_/ v0.0.3

                projectdiscovery.io

{"timestamp":"2023-02-01T14:36:55.8177568+01:00","endpoint":"https://hackerone.com/","source":"http://hackerone.com","tag":"header","attribute":"location","source-technologies":["Cloudflare"]}
{"timestamp":"2023-02-01T14:36:56.1390534+01:00","endpoint":"https://www.hackerone.com/","source":"https://hackerone.com/","tag":"header","attribute":"location","source-technologies":["Cloudflare","HSTS","Amazon S3","Amazon Web Services"]}
...

Note: the technologies are relative to the parsed response that generated future navigation requests (promises), just like other attributes (tag, attribute)

[ehsandeep]

@Mzack9999 apologies if it was unclear in the issue, but the idea is to discover technology information of the endpoint (when available) instead of the source.

I mentioned when available as we might not have access to response data for every newly discovered endpoint, so populating tech info of crawled endpoint would be sufficient.

For example:

{"timestamp":"2023-02-01T14:36:55.8177568+01:00","endpoint":"https://www.hackerone.com:443/sites/default/files/styles/logo_band_white/public/GM2X_0.png.webp?itok=_mTFOxRw","source":"http://hackerone.com","tag":"header","attribute":"location","endpoint-technologies": ["Cloudflare","Fastly","HSTS","MariaDB","Nginx","PHP","Pantheon","Varnish"]}
{"timestamp":"2023-02-01T14:36:56.1390534+01:00","endpoint":"https://www.hackerone.com:443/knowledge-center/what-vulnerability-assessment-benefits-tools-and-process","source":"https://hackerone.com/","tag":"header","attribute":"location","source-technologies":["Amazon S3","Amazon Web Services","Cloudflare","Fastly","Google Tag Manager","HSTS","Lever","MariaDB","Nginx","PHP","Pantheon","React","Varnish"]}

[Mzack9999]

@ehsandeep this is impossible by design, katana implementations spits out discovered and not yet visited endpoints. I'm tracking the requested change (which will unlock issues such as #248) at #303

[ehsandeep]

This will be reworked later as detailed here - #303