Label spans that have errors attached

[ankur22]

We already have spans for some of our APIs, such as page.screenshot. This allows us to visualise the test run and all the metrics that go along with a particular navigation. What we're currently missing are the errors on the spans. For example, when page.screenshot is called, and an error is received from a remote server (when uploading screenshots to a remote server) we should mark the span with the error.

Tasks

Preview Give feedback

1. Refactor APIs that are traced #1259
   +0
2. Add errors to spans #1260
   +0
3. Add recent browser PR merges to release notes k6#3709
   +0

[ankur22]

I think this involves the following calls:

	span.SetStatus(codes.Error, "rate limit reached")
	span.RecordError(errors.New("429: Too Many Requests"))

We need to check the best practices to make sure we're not missing anything.

EDIT

I checked on the otel site and the way that was proposed in the example above it correct -- source.