No warning(s) in the output file with report command (quiet mode)

[DjinnS]

What did you implement:

When there are one or more warnings during the scan, they appear in the report especially in the file "summary.txt" (with the option "-to-localfile").
I want to parse the content of this file to process the scan result. With warnings the parsing is more complicated. Furthermore errors and warnings appear in the logs.

We keep track of the errors and warnings with the command scan, but we could remove them from the command report.

So I added an option -quiet to force logging to a file instead of stdout.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

In my case warnings appear when I scan a debian container because checkrestart ins't available (for example). Use -quiet option when there are warnings during your scan, with the option -to-localfile and you would see that there aren't warnings in the file (juste results of the scan).

Checklist:

You don't have to satisfy all of the following.

• Write tests
• Write documentation
• Check that there aren't other open pull requests for the same issue/feature
• Format your source code by make fmt
• Pass the test by make test
• Provide verification config / commands
• Enable "Allow edits from maintainers" for this PR
• Update the messages below

Is this ready for review?: YES