E2E Test - Tracing through ApiServerSource

[Harwayne]

This should not be started until after #1758 is closed.

Problem
In order to ensure that ApiServerSource generates traces correctly, we need an E2E test.

Persona:
Contributor

Exit Criteria
A test in the e2e suite that runs before every PR merge. The test verifies that an event sent from an ApiServerSource sent to something that doesn't emit traces (e.g. a simple web server) still creates a trace with a span for the communication between ApiServerSource and its sink.

[Harwayne]

/project Observability To do

[n3wscott]

similar to https://github.com/knative/eventing/blob/master/test/conformance/broker_tracing_test.go and https://github.com/knative/eventing/blob/master/test/conformance/channel_tracing_test.go.

/good-first-issue

[knative-prow-robot]

@n3wscott:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

similar to https://github.com/knative/eventing/blob/master/test/conformance/broker_tracing_test.go and https://github.com/knative/eventing/blob/master/test/conformance/channel_tracing_test.go.

/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.