`JenkinsTest` is intermittent

When `JenkinsTest` runs on `ci.jenkins.io` it intermittently fails with:

```
10:32:15 [ERROR] org.waveywaves.jenkins.plugins.tekton.client.build.create.JenkinsTest.testFreestyleJobWithExpandedYamlInput Time elapsed: 1.599 s <<< FAILURE!
10:32:15 java.lang.AssertionError:
10:32:15
10:32:15 Expected: a string containing "Whoop! This is the pod log"
10:32:15 but: was "Legacy code started this job. No cause information is available
10:32:15 Running as SYSTEM
10:32:15 [EnvInject] - Loading node environment variables.
10:32:15 Building in workspace /home/jenkins/workspace/gins_tekton-client-plugin_PR-147/target/tmp/jenkinsTests.tmp/jenkins5080825060315866721test/workspace/p
10:32:15 Deleting existing workspace /home/jenkins/workspace/gins_tekton-client-plugin_PR-147/target/tmp/jenkinsTests.tmp/jenkins5080825060315866721test/workspace/p
10:32:15 Staging file:/home/jenkins/workspace/gins_tekton-client-plugin_PR-147/target/test-classes/org/waveywaves/jenkins/plugins/tekton/client/build/create/tekton-test-project.zip
10:32:15 [Checks API] No suitable checks publisher found.
10:32:15 [Tekton] Pod test/hello-world-pod
10:32:15 [Tekton] Pod test/hello-world-pod - Running...
10:32:15 [Tekton] Container hello-world-container
10:32:15 [Tekton] Container hello-world-container - Completed
10:32:15 W[Tekton] Pod test/hello-world-pod Status: Succeeded
10:32:15 [Tekton] Completed PipelineTask pipelineTaskName
10:32:15 hoop! This is the pod logFinished: SUCCESS
10:32:15 "
10:32:15 at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
10:32:15 at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6)
10:32:15 at org.waveywaves.jenkins.plugins.tekton.client.build.create.JenkinsTest.testFreestyleJobWithExpandedYamlInput(JenkinsTest.java:427)
10:32:15 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
10:32:15 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
10:32:15 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
10:32:15 at java.lang.reflect.Method.invoke(Method.java:498)
10:32:15 at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
10:32:15 at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
10:32:15 at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
10:32:15 at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
10:32:15 at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
10:32:15 at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:548)
10:32:15 at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)
10:32:15 at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)
10:32:15 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
10:32:15 at java.lang.Thread.run(Thread.java:748)
```

Start with JenkinsTest.testFreestyleJobWithExpandedYamlInput at JenkinsTest.java:427 and reproduce the intermittent failure on ci.jenkins.io. Compare the expected pod-log text with the actual Jenkins build log, then rerun the test to verify it consistently detects "Whoop! This is the pod log".

Written by the indexing model from the issue text.