Multi grep in version detection

[m-1-k-3]

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Feature

• What is the current behavior? (You can also link to an open issue here)

see #980

• What is the new behavior (if this is a feature change)? If possible add a screenshot.

closes #980

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Yea ... we can not define more complex version identifier rules :)

libtasn;multi_grep;unknown;'"LIBTASN1 ERROR:"&&"^[0-9](\.[0-9]+)?+$"';"sed -r 's/([0-9](\.[0-9]+)+?)$/libtasn1:\1/'";

Module s09 now checks first for LIBTASN1 ERROR: and if this is found it checks for the second identifier ^[0-9](\.[0-9]+)?+$

• Other information:

This PR is work in progress and needs some more testing ...

[m-1-k-3]

During the testphase it is possible to see the matching sub identifiers

GZIP is the first identifier that matches
Written by ... is the 2nd
Report bugs to ... it the 3rd
and the final identifier is the version number 1.3.12

[m-1-k-3]

This is a huge step in our version detection engine. Currently it is only implemented for ELF files in the S09 module
In the future we should also implement this mechanism for s115/s116 and also for the other mechanisms in S09. At the end this will completely replace the strict mode! h00ray