Add line numbers when reporting artifact locations

[alfredodeza]

What would you like to be added: In addition to file paths, line numbers are crucial for some integrations like IDEs. Ideally, in the JSON presenter in the same place where file paths are defined.

For example:

   "locations": [
    "test/integration/test-fixtures/image-debian-match-coverage/ruby/Gemfile.lock"
   ]

Could be an object:

    "locations": [
        {
            "path": "test/integration/test-fixtures/image-debian-match-coverage/ruby/Gemfile.lock",
            "linenumber": 13
        }
    ]

One potential problem here is that there are cases where a line number is not possible at all. For example in an RPM database. In those situations it is fine to use nill.

Why is this needed: Some integrations like IDE would benefit from having line numbers so that they can highlight where the detected package exists

Additional context:

[wagoodman]

This is relevant to SARIF output which supports noting line numbers in the output as well as being able to express better source code-like analysis in the future.

[tomerse-sg]

can be a nice feature for integrations like Github and helping developers to fix some issues.