feat: add docker path mappings for remote and monorepo workflows

[William-Blackie]

Summary

Add host/container path mapping support for remote Python commands, including Docker-oriented DAP attach hooks, translated result paths, and docs/examples for general and monorepo setups.

Problem

neotest-python currently assumes Neovim and the Python test process share the same filesystem. That breaks for Docker and other remote execution flows where test ids, helper scripts, temp files, and debug paths need to move cleanly between host and container paths.

Solution

This change adds path_mappings, cwd, env, and function-based dap hooks so the adapter can run against remote Python entrypoints while still reporting results back to host paths.

It also:

• translates temp files, script paths, test ids, and output paths in both directions
• derives debugpy pathMappings for attach flows
• supports dynamic configuration for broader monorepo use cases
• documents Docker and monorepo examples
• adds Lua coverage for path translation and adapter spec generation

This is still a work in progress, but feedback is welcome. The intent is to keep this generally useful for both standard repositories and monorepos rather than tailoring it to one Docker layout.

Reviewer notes

The main areas worth pressure-testing are:

• path translation edge cases for temp files and nested mappings
• whether the dap callback/context shape is the right long-term API
• whether the monorepo/root override examples match real-world adapter usage