Trace bundle execution

[carolynvs]

Now that tracing is supported in #1831 the full bundle execution path should be supported. Right now we have a trace when a bundle starts/stops. But we don't have any insight into the bundle's execution. It would be great if we could see each mixin step's execution and runtime logs from porter-runtime.

If we passthrough the standard open telemetry environment variables that will work great for a listener that is not on localhost. For example, if the listener is on a public ip or domain name, then the container can reach it. For localhost listeners though, we will need to get creative since "localhost" won't resolve to the host from the container. This is mainly a concern for local development though, so if we just make it work for public listeners, that would be a great start.

[carolynvs]

TIL about host.docker.internal which lets you refer back to the docker host from inside a container. 🎉