Improve error handling of Theodolite

This applies in particular when running in a Kubernetes job. For example, trying to access Kubernetes resources in a not-allowed namespace results in errors, which are not properly caught. This should be considered for #101 (closed).

changed milestone to %0.3.0

added modul/theodolite label

changed the description

Maybe I was wrong in this regards. Exceptions are caught are meaningful error messages are printed. We might should consider to set another default backoffLimit, perhaps 0.

changed milestone to %0.4.0

This will probably become obsolete with !83 (merged).

removed milestone %0.4.0

Becomes obsolete with !159 (merged). Further process on this in our new implementation is tracked by #236 (closed).

closed