fix: create jaeger ExternalName services in train-ticket setup job

[somyas25]

Problem

The train-ticket pods crash on startup if the Jaeger ExternalName services don't exist in the train-ticket namespace before deployment. The conductor's create_external_name_service() runs after app.deploy(), which is too late for train-ticket.
More details about the problem are described in this issue #558.

Fix

I added an initContainer to the existing train-ticket-deploy job that creates the Jaeger ExternalName services before the main deploy container starts. The initContainer checks if each service already exists before creating it so that it works correctly regardless of whether the services were already created by the conductor or didn't exist yet.

Testing

I ran problem 17 containing train-ticket application deployment to check if it correctly works.

Previous Attempt

I tried adding ExternalName services directly to the Helm chart template: caused Helm ownership conflicts.