Change RunDefaultContainerAndStopOnCleanup to use the interface testing.TB

[jordcarfetch]

This allows test-containers to be used in benchmark setup code.
While it's generally recommended to isolate the code one is benchmarking, profiling the end to end logic of a handler can still reveal bottlenecks and extra memory allocations.

This change is backwards compatible, as *testing.T is an implementation of testing.TB.

References

• interface testing.TB

Submitter checklist

• Recommended: Join WireMock Slack to get any help in #help-contributing or a project-specific channel like #wiremock-java
• The PR request is well described and justified, including the body and the references
• The PR title represents the desired changelog entry
• The repository's code style is followed (see the contributing guide)
• Test coverage that demonstrates that the change works as expected
• For new features, there's necessary documentation in this pull request or in a subsequent PR to wiremock.org

[jordcarfetch]

I have an in-mem caching http client I need to benchmark -- just the first request goes over the wire during setup. I could mock or inject at a more granular level, but then the profiling is less realistic.

[oleg-nenashev]

Works on my machine, and thanks!
I plan some potentially planning to do some breaking changes in the next release too, so it should be fine in any case