support multiple vulnerability database strategies (github advisory and dependency-check)

[mthbernardes]

Support Github advisory database.

Pros

• Faster execution.
• Lookup by dependency-name.
• Possible to generate a binary using graalvm.
• Not necessary to mantain a DB like in dependency-check.
• Code much more simple.

Cons

• Lookup vulnerabilities by dependency name so in case of a dependency with a different name in the advisory it will not find the vulnerability (E.g.: org.jdom/jdom2 / org.jdom/jdom)
• Github token necessary
• Rate Limit
• It's possible to execute it using a Github action token but it has a rate limit of 5k.

Issues

• Support git version when looking up for fixes.