Logs v2 (pre-release) - edge-cases

[tkonieczny]

Describe the bug
Combined issue for multiple cases noticed while checking logs v2 (pre-release).

• timeout
  https://demo.testkube.dev/tests/expected-fail-jmeter-timeout/executions/66055ff99be5665230d95d4a

can't start test job pod: pods "66055ff99be5665230d95d4a-mbdq5" not found
can't read data from pod, pod was not completed: pods "66055ff99be5665230d95d4a-mbdq5" not found
analyzing test results and artfacts
pods "66055ff99be5665230d95d4a-mbdq5" not found
stopping execution
execution stopped
test execution failed: %!w(*errors.StatusError=&{{{ } {   <nil>} Failure pods "66055ff99be5665230d95d4a-mbdq5" not found NotFound 0xc006320de0 404}})

• incorrect checkout dir:
  https://demo.testkube.dev/tests/expected-fail-container-executor-k6-wrong-dir/executions/66055ff99be5665230d95d47

test container message:  reason: Error
exit code: 255
test container message:  reason: Error
exit code: 255

• logs are ocassionally missing after execution
  https://demo.testkube.dev/tests/expected-fail-curl-executor-incorrect-uri/executions/66056c1eb1fa3322628cd17f
  Initially full logs were available (created kubernetes job, waiting for pod to spin up, ... Initializing..., etc.)
  But, after execution it's just:

response status don't match expected 418 got 200

The same with up to date CLI - only ⨯ response status don't match expected 418 got 200

• can't read data from pod, pod was not completed: - is actual reason missing here?
  https://demo.testkube.dev/tests/expected-fail-post-run-script/executions/66055ff99be5665230d95d4d

:x: Execution failed: process started with command: /bin/sh, exited with code:128  error: exit status 128
output: ===== post-run script - EXPECTED FAIL

can't read data from pod, pod was not completed: 
analyzing test results and artfacts

stopping execution
execution stopped
starting execution expected-fail-expected-fail-post-run-script-561 (66055ff99be5665230d95d4d)

https://demo.testkube.dev/tests/expected-fail-pre-run-script/executions/66056609b1fa3322628cd130

===== pre-run script - EXPECTED FAIL

:x: Execution failed: process started with command: /bin/sh, exited with code:128  error: exit status 128
output: ===== pre-run script - EXPECTED FAIL

process started with command: /bin/sh, exited with code:128  error: exit status 128
output: ===== pre-run script - EXPECTED FAIL

can't read data from pod, pod was not completed: 
analyzing test results and artfacts

stopping execution
execution stopped

• ✔️ OOMKIlled
  https://demo.testkube.dev/tests/expected-fail-cypress-oomkilled/executions/66055ff99be5665230d95d4b

:x: Execution failed: process started with command: npm, exited with code:-1  error: signal: killed
output: 
can't read data from pod, pod was not completed: 
analyzing test results and artfacts

stopping execution
execution stopped
starting execution expected-fail-expected-fail-cypress-oomkilled-961 (66055ff99be5665230d95d4b)

• ✔️ ( (updated UI)) starting execution ASDFASDFASDF is displayed at the end of logs
  https://demo.testkube.dev/tests/expected-fail-pre-post-run-script/executions/66055ff99be5665230d95d50

stopping execution
execution stopped
starting execution expected-fail-expected-fail-pre-post-run-script-244 (66055ff99be5665230d95d50)

https://demo.testkube.dev/tests/expected-fail-container-post-run-script/executions/66055ff99be5665230d95d4f

===== post-run script - EXPECTED FAIL
starting execution expected-fail-expected-fail-container-post-run-script-245 (66055ff99be5665230d95d4f)