Move JENKINS-33258 tests into CLI specific tests

[MarkEWaite]

Move JENKINS-33258 tests into CLI specific tests

The assertions are checking log messages that are only available from CLI git. No reason to spend time or energy calling methods that won't generate the necessary logging output.

Checklist

• I have read the CONTRIBUTING doc
• I have added tests that verify my changes
• Unit tests pass locally with my changes
• I have added documentation as necessary
• No Javadoc warnings were introduced with my changes
• No spotbugs warnings were introduced with my changes
• I have interactively tested my changes

Types of changes

• Infrastructure change (non-breaking change which updates dependencies or improves infrastructure)

@rishabhBudhouliya this was an assertion that was missed in the transition from JUnit 3 to JUnit 4. The assertion after the test completes was too subtle. I like the JUnit 4 style that is expressed in this test now. It makes explicit checks within the individual test, instead of performing checks at the end of every test.