…on a context that still exists by the time the test assertion runs

This reverts commit b47ab26.

explicitly set expected config because config can leak between tests

…atibility with tests that rely on the root span continuing to exist

make reset_listeners affect ancestors

…sistent contextvars behavior in 2.7

…f after"

This reverts commit d584690.

…races not to be written during tracer.shutdown()

test this hypothesis by skipping the management of _CURRENT_CONTEXT for contexts created by spans

…e it is known to perform fine, and storing context on spans is a stopgap measure anyway

…odifyitems`` (#6236)

CI Visibility: Switch Intelligent Test Runner from test skipping mode to
test suite skipping mode.

The main reason to use this approach over doing test suite skipping with
``pytest_ignore_collect`` hook or skipping the tests individually inside
``pytest_runtest_protocol`` hook is that this hooks allows us to add the
skip marker before ``pytest_runtest_protocol`` is run, so we can decide
wether to create the span for it or skip it altogether.

This PR skips the creation of spans for skipped tests, suites and
modules, to act as the rest of the languages act while using ITR.

Main changes it involves:

1. Coverage is now measured and sent by test suite instead of test,
hence dropping the ``cover`` context manager that could be used inside
the ``pytest_runtest_protocol`` hook to a singleton to be reused until
the test suite finishes.
2. By leveraging the ``pytest_collection_modifyitems`` hook, we can add
skip markers to the tests right after the test collection step, so we
have that information at ``pytest_runtest_protocol`` hook.
3. Some changes in the requests to the backend, to specify we want the
skippable tests at test suite level.

Since ITR is not yet beta it doesn't have a release note.

## Checklist

- [x] Change(s) are motivated and described in the PR description.
- [x] Testing strategy is described if automated tests are not included
in the PR.
- [x] Risk is outlined (performance impact, potential for breakage,
maintainability, etc).
- [x] Change is maintainable (easy to change, telemetry, documentation).
- [x] [Library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
are followed. If no release note is required, add label
`changelog/no-changelog`.
- [x] Documentation is included (in-code, generated user docs, [public
corp docs](https://github.com/DataDog/documentation/)).
- [x] Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))

## Reviewer Checklist

- [x] Title is accurate.
- [x] No unnecessary changes are introduced.
- [x] Description motivates each change.
- [x] Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes unless absolutely necessary.
- [x] Testing strategy adequately addresses listed risk(s).
- [x] Change is maintainable (easy to change, telemetry, documentation).
- [x] Release note makes sense to a user of the library.
- [x] Reviewer has explicitly acknowledged and discussed the performance
implications of this PR as reported in the benchmarks PR comment.
- [x] Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)

…tead

…sgi-no-context-data-on-spans

…sgi-no-context-data-on-spans

…/flask-no-iast

…o-asm-context

…sgi-no-context-data-on-spans

…t.butler/flask-wrappers-no-asm

…/flask-no-iast