Add benchmarks to every type of package in build workflow

[NathanielRN]

In #243 we add performance tests for the AWS SDK Extension.

The AWS SDK extension falls under the category sdkextension of tests matched in the build workflow. For this reason, when the jq command looks through the entire repo after the workflow for *-benchmark.json files we are guaranteed to find at least ` file. This file is then given to the subsequent Github action to report on benchmarking results.

However, the build workflow also has instrumentation and exporter packages. These don't have performance tests yet so the jq command will fail. Even if we suppress the failure, the subsequent GitHub action will fail if no valid output.json file is created.

A temporary solution was to only run those 2 steps of the workflow if: matrix.package == 'sdkextension'. A more long-term solution will be to add benchmarks to instrumentation and exporter.

opentelemetry-python-contrib/.github/workflows/test.yml

Lines 61 to 62 in 91bfc9a

	# TODO: Add at least one benchmark to every package type to remove this
	if: matrix.package == 'sdkextension'

and

opentelemetry-python-contrib/.github/workflows/test.yml

Lines 68 to 69 in 91bfc9a

	# TODO: Add at least one benchmark to every package type to remove this
	if: matrix.package == 'sdkextension'

We know only these packages are required because as long as subsequent tests fit under these categories we won't have to keep adding if statements.

[github-actions]

This issue was marked stale due to lack of activity. It will be closed in 30 days.

[github-actions]

Closed as inactive. Feel free to reopen if this issue needs resolving.

[NathanielRN]

We should probably keep this open until we have benchmarks for all relevant contrib packages (and a relevant way to force new packages to include them)!

@lzchen @codeboten

[lzchen]

@NathanielRN
If you are interested in adding these benchmarks, feel free to create PRs for them and we'll be happy to review them :)