Fix container spawning timing out on eos configuration

Summary

While running jobs on the cirunners, it happens relatively frequently that the job fails because the containers are not spawned properly. Specifically, it will time out while waiting for EOS to be configured and then fail the job. See https://gitlab.cern.ch/cta/CTA/-/jobs/41919735

Steps to reproduce

Run a pipeline job (specifically one of the kubernetes test ones) and it might fail.

What is the current bug behaviour?

The job fails due to the EOS configuration timing out.

What is the expected correct behaviour?

The containers should be spawned properly and not produce an error.

Relevant logs and/or screenshots

Creating pods in instance
pod/init created
Waiting for init.................................................OK
Launching pods
pod/client created
pod/ctacli created
pod/tpsrv01 created
pod/tpsrv02 created
pod/ctaeos created
pod/ctafrontend created
pod/kdc created
Waiting for other pods..OK
Waiting for KDC to be configured..OK
Configuring KDC clients (frontend, cli...) OK
klist for client:
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: user1@TEST.CTA
Valid starting     Expires            Service principal
08/02/24 01:07:34  08/03/24 01:07:34  krbtgt/TEST.CTA@TEST.CTA
klist for ctacli:
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: ctaadmin1@TEST.CTA
Valid starting     Expires            Service principal
08/02/24 01:07:34  08/03/24 01:07:34  krbtgt/TEST.CTA@TEST.CTA
Configuring cta SSS for ctafrontend access from ctaeos..................OK
Waiting for EOS to be configured............................................................................................................................................................................................................................................................................................................TIMED OUT
422
FAILURE: cleaning up environment