Add the ability to disable spryker's jenkins/jenkins-runner in dev and CI but still build and push for pipeline

[andytson-inviqa]

We don't always need jenkins/jenkins runner in development, and it's never tested in CI, but it consumes a lot of memory.

If we can prevent it being built in dev (easy to do), but build and not run it in CI (difficult to do), then it can still be pushed for pipeline.

While jenkins is a beast, cronie instead is not suitable for docker due to there being so many spryker jobs that can run at the same time (multiplied by number of stores as well), which can easily cause an out of memory event on the pod or host.

Contrast to that, Jenkins at least limits the number of concurrent jobs on an runner, and can scale multiple runner pods. The only nearest thing close to that is k8s cronjobs with a resourcequota limiting the concurrency.