Option to output violation information of skipped tests/lines

Problem to Solve
Without the complete violation information, we cannot know whether certain tests or lines are being skipped reasonably. This option allows us to make more informed judgements.

Proposed Solution

1. Our team works with the SARIF output format. Therefore, it's desirable if Bandit could output to SARIF directly when used with the flag -f sarif.
2. When Bandit is executed with the combination of flags -f sarif and --output-suppression, it should run all lines in a file against not only the tests to include specified via -t (command line) / tests (external command line argument & external configuration file), but also the tests specified to be skipped via -s (command line) / skips (external command line argument & external configuration file).
3. In the SARIF output of Bandit, aside from the original content it normally contains, there should also be violations caused by "skipped" tests and lines, along with the kind and justification of a skipped test (a.k.a. suppression in SARIF terms). Here is an example:
   
4. Ideally every skipped test/line should have an accompanying explanation (justification), as my colleague André stated in #478. We are also willing to contribute to this.

Alternatives
As said in #646, if the SARIF output is planned to be included in the near future, our team would be happy to contribute. If not, we are okay with modifying bandit-sarif-formatter together as well.

Please let us know what you think. Thank you.

No files or tests are named in the issue. Start by locating Bandit's current formatter and handling of -t/-s with --output-suppression, then review bandit-sarif-formatter and the SARIF suppression fields cited here. Done means SARIF output includes skipped-test and skipped-line violations with suppression kind and justification while preserving normal output.