Add Additional testing on functionality of the Bandit tool

Is your feature request related to a problem? Please describe.
test_no_new_candidates().
To improve the functional test suite, you can add additional test cases for the remaining functionality of the Bandit tool. Here are some suggestions for additional test cases

Describe alternatives you've considered
Considering all of these test cases id like to implement:

• Test, when there are new candidates, found compared with those in the baseline. This should return the new candidate details along with the candidates from the baseline.

• Test when a candidate has a # nosec comment added and that candidate was previously flagged as an issue in the baseline. This should not return that candidate in the results.

• Test when a candidate has been fixed in the code and should no longer be flagged as an issue in the baseline. This should not return that candidate in the results.

Additional context
To implement these changes, you can add additional test methods to the BaselineFunctionalTests class, similar to the existing test_no_new_candidates() method.

Love this idea? Give it a 👍. We prioritize fulfilling features with the most 👍.

Start with test_no_new_candidates() in the BaselineFunctionalTests class and review how the existing functional test exercises Bandit's baseline behavior. Add coverage for new candidates, candidates suppressed by a # nosec comment, and candidates fixed since the baseline. Done means each case returns the expected candidate results, with suppressed or fixed candidates excluded.