feat #1092: Validate binary values + precompile them as well

[Ice3man543]

Proposed changes

Closes #1092

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)

[forgedhallpass]

The associated ticket was about validating hex values from templates when the -validate flag is used. Instead of doing so, this PR seems to change the functionality itself. Have you checked if content highlighting with the -debug flag still works after this change?

[Ice3man543]

Basically what i did was move the binary hex decoding to the Compile function which returns errors if it finds an invalid sequence, similar to what we do for regexes. It should not really have an impact on coloring as that part is not touched.

[forgedhallpass]

You are right, when I looked at the code I relied on the name of the variable hexa, which in fact holds binary data. Also the Binary field in the matcher is confusing, because it actually contains the data in hexadecimal format. Another reason why having meaningful variable names is important...

[ehsandeep]

echo 1.1.1.1 | ./nuclei -t a.yaml -validate

                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   2.5.4-dev

		projectdiscovery.io

[WRN] Use with caution. You are responsible for your actions.
[WRN] Developers assume no liability and are not responsible for any misuse or damage.
[ERR] Error occurred parsing template test.yaml: could not compile request: could not compile operators: could not compile matcher: could not hex decode binary: 00700000200000002000000
[FTL] Could not run nuclei: an error occurred during templates validation