Add output which service triggered scan

[ikstream]

I think it would be a good addition to have another field in the commands.csv that provides information which service tag in the service.xml caused the actual scan. This would help to get an overview on large scans which service tags have been processed at least to some extend.

[4elta]

what do you mean with "service tag"?

anyway, this isn't such a trivial task:

• a single service (i.e. the tupple of transport protocol, port, application protocol) could trigger multiple scans
• a scan command could have been triggered by multiple services; though, most of the time the command will only be run once

how should we handle these issues, iff we really want to implement such a feature?

[ikstream]

The solution for #64 basically suites this well enough to keep it simple.