Schema Change: Add defense

[WebBreacher]

Like @3xp0rt mentioned in #855 , we should be tool/framework agnostic and provide the data so that the downstream tools can parse or ignore as their capabilities allow.

My thought is to add a single element protection to the schema. It would have several values like:

• cloudflare = Meaning the site is behind CloudFlare's protections
• userauth = Meaning that a tool may need to authenticate to the site as a valid user to check this entry.
• captcha = Meaning the site employs some kind of CAPTCHA that may prevent some automated tools from being successful
• multiple = The site may use multiple defensive measures.
• other = Anything else

Tool makers could ignore this field and just try to check the site or, if they use certain evasion/checking techniques, could change tool behavior to be more successful in checking the site.

I would be interested in people's thoughts here. And thanks for thinking about this @3xp0rt.

[WebBreacher]

OK. No comments. We move forward then.

[WebBreacher]

#879 adds this.

[WebBreacher]

cc: @C3n7ral051nt4g3ncy @yooper @K2SOsint @AXRoux @grabowskiadrian @p1ngul1n0 @swedishmike