Gate non-breaking releases on OpenTelemetry Falcon integration

OpenTelemetry Falcon instrumentation plugin could be a good example of a large 3rd party integration we might want to make sure not break. See also: https://github.com/falconry/falcon/issues/259

OpenTelemetry Falcon 3.0 support: https://github.com/falconry/falcon/issues/1828

This could be something basic (similar to https://github.com/open-telemetry/opentelemetry-python-contrib/blob/master/instrumentation/opentelemetry-instrumentation-falcon/tests/test_falcon.py, alternatively just a copy of it), or something more advanced running a reference collector in the E2E fashion.

Review the linked Falcon issue 259, Falcon 3.0 support issue 1828, and the OpenTelemetry test_falcon.py example. Compare the basic copied-test approach with the reference-collector E2E option, then identify the repository's release-gating entry point. Done means non-breaking releases exercise Falcon integration coverage and fail when that integration breaks.

Written by the indexing model from the issue text.