Reconsider passing a full span as param

[Mierdin]

As an example, the getJobStatus function accepts a full span as a parameter, rather than a span context.

I believe I did this to keep noise down for lower-level things like health checks, in that I didn't believe these functions warranted a separate span, when I really just needed them to log to a parent span.

Two things should be done:

• Document everywhere this is being done. Should only be a handful of places if memory serves. If people will be expecting each function to have its own span, I want to be able to tell them the few times this won't be true.
• Consider if its appropriate to keep this way, or change to a context. The trick will be balancing what's "standard" with what keeps tracing noise down.