Add error log option

[zerodivisi0n]

Proposed changes

Implements error log feature (#1187)

Original issue checklist:

• Updating id to template-path to include template path information instead of id (933ed24, 463c1c0)
• Updating url JSON field input to make it uniform for all types of template (933ed24)
• Updating HTTP and FILE type error to include only final error information (1eb0378)

Differences from the original issue:

• The absolute path to the template is displayed, not the relative path as in the example. Does this need to be fixed?
• I made the original error message for all protocols since it can be done uniformly in one place. Also, I am doing recursive Unwrap to get the last wrapped error. I don't know how bad it is.
• I also did some refactoring to improve the testability of outputs. This is done in the last three commits (cd2db28, b8ebbc2, bccc8e9). If it's unnecessary, I can remove it.

Example of output:

$ echo "https://exxmple.com/tcpconfig.html" | ./nuclei -t misconfiguration/tcpconfig.yaml -error-log error.log
$ cat error.log | jq                                                                                                               
{
  "template": "/home/zerodivisi0n/nuclei-templates/misconfiguration/tcpconfig.yaml",
  "input": "https://exxmple.com/tcpconfig.html/tcpconfig.html",
  "error": "no address found for host",
  "type": "http"
}

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]

Everything working well as described in the issue @zerodivisi0n 👏🏻

[Ice3man543]

The PR looks good to me, very nice work @zerodivisi0n!

[Ice3man543]

Regarding showing absolute paths, i guess it's okay for us to show absolute paths since those would be easy to open through the error log. Also unwrapping like that is the accepted way of getting the last error, so It shouldn't be an issue.
The tests for output layer also can be merged!

[zerodivisi0n]

@ehsandeep , @Ice3man543 , great! Thanks for the quick review!