For multistep tests one of steps fails with error of not found pod

[vsukhin]

Describe the bug
For multistep tests one of steps fails with error of not found pod

To Reproduce
Steps to reproduce the behavior:

1. Run 'kubectl testkube tests start multi-step-test'
2. Check execution results 'kubectl testkube tests execution some-execution-id'
3. See error run script: script execution failed: pods pod-name not found

Expected behavior
Test step execution results shoud be returned from job pod - either failed or success one

Version / Cluster

• Testkube version - 0.8.3
• Kubernetes cluster - local Minikube
• Kubernetes version 1.22.3

Api server logs:
{"level":"error","ts":1643200578.358768,"caller":"jobs/jobclient.go:101","msg":"poll immediate error","error":"pods "61f13f5492d305b4cc3a4764--1-n28fp" not found","stacktrace":"github.com/kubeshop/testkube/pkg/jobs.(*JobClient).LaunchK8sJobSync\n\t/build/pkg/jobs/jobclient.go:101\ngithub.com/kubeshop/testkube/pkg/executor/client.JobExecutor.ExecuteSync\n\t/build/pkg/executor/client/job.go:105\ngithub.com/kubeshop/testkube/internal/app/api/v1.TestKubeAPI.executeScript\n\t/build/internal/app/api/v1/executions.go:97\ngithub.com/kubeshop/testkube/internal/app/api/v1.TestKubeAPI.executeTestStep\n\t/build/internal/app/api/v1/tests.go:291\ngithub.com/kubeshop/testkube/internal/app/api/v1.TestKubeAPI.executeTest.func1\n\t/build/internal/app/api/v1/tests.go:235"}

[vsukhin]

Closed in #877 by changing backoff limit to 0 for executor job