XML (JUnit) output is not recognized by Bamboo JUnit parser

Describe the bug
Bandit's XML/Junit output is not recognized by the Bamboo Junit parser when there is no violation.
The reason is that the Junit parser is expecting at least one TC, which kinda makes sense.

Exact error

Failing task since test cases were expected but none were found.

To Reproduce
Steps to reproduce the behavior:

Create a report without any finding
For example

bandit . --format xml
[main]	INFO	profile include tests: None
[main]	INFO	profile exclude tests: None
[main]	INFO	cli include tests: None
[main]	INFO	cli exclude tests: None
[main]	INFO	running on Python 3.6.13
[manager]	WARNING	Skipping directory (.), use -r flag to scan contents
<?xml version='1.0' encoding='utf-8'?>
<testsuite name="bandit" tests="0" />%

Pass this result to the JUnit parser in Atlassian Bamboo.

Expected behavior
No errors from the parser side.

Bandit version

bandit 1.7.0
  python version = 3.6.13 (default, May 17 2021, 16:38:03) [GCC Apple LLVM 12.0.5 (clang-1205.0.22.9)]

Additional context
I completely understand that this may not be accepted, however, I wanted to raise this as more people may struggle with this scenario. Would be nice if we have an option to create one dummy test case that will satisfy CI.

Start by reproducing bandit . --format xml with no findings and inspect the generated JUnit XML, especially the empty testsuite output. Compare that result with Bamboo's JUnit parser expectation; done means a no-violation report is accepted without parser errors.