Using frame inspection to obtain feature file path is unreliable

Pytest-bdd uses frame inspection to obtain the path to its feature file. This in unreliable because

Pytest performs assert rewriting, and caches the rewritten modules. If I run pytest-bdd on my local system, where my tests are in "/projects/my-project/tests", then the cached rewritten modules will end up containing this path in their metadata.

If I then spin up a docker container, with my project mounted as "/app/my-project", then when I run my tests, pytest will load the cached rewritten modules, and the metadata will be wrong. This usually doesn't matter, but it matters to pytest-bdd, because pytest-bdd will get the wrong path, and go looking for its feature file in "/projects/my-project/tests/....", and crash with a FileNotFoundError.

Start by tracing pytest-bdd's frame inspection and how pytest's assert-rewritten module cache supplies feature-file paths. Reproduce the failure by running tests under /projects/my-project/tests, then in a Docker container mounted at /app/my-project. Done means cached metadata no longer sends pytest-bdd to the stale path and the FileNotFoundError is avoided.