Improve Django Unit Test Execution Pathing

[danielebra]

When running neovim somewhere other than where manage.py is located can cause pathing issues when running tests. I think this can be improved by identifying where manage.py is located, relative to the test file location.

Consider the existing solution:

# Make sure we can import relative to current path
sys.path.insert(0, os.getcwd())

It will place the cwd of neovim into the system path, before executing the test.

Given a repository such as:

app/
├── manage.py
├── app/ 
│   ├── __init__.py
│   ├── settings.py
│   ├── urls.py
│   └── wsgi.py
├── foo/
│   ├── __init__.py
│   ├── models.py
│   ├── views.py
│   └── tests/
│       └── test_foo.py
└── bar/
    ├── __init__.py
    ├── models.py
    ├── views.py
    └── tests/
        └── test_bar.py

and with neovim launched from top of the repository and a test being ran in bar/tests/test_bar.py

it would result in a case_id:

/path/to/repo/app/bar/tests/test_bar.py::Something::test_something

that then results in an argv generation of

['neotest-python', 'app.bar.tests.test_bar.Something.test_something']

Note the prefix of app, which is the django project housing project in the given repository structure example

This would be different to what would of occured if the tests were ran with manage.py, because the path would start with bar instead of app.

In the current solution, one way around this is to cd into the app folder, before triggering neotest to run the test.

This pull request proposes adding a resolver to locate manage.py and perform relative file calculations from the location of manage.py, rather than the location of neovim's cwd

@afrischk this extends your implementation, what do you think? #51

[afrischk]

@danielebra Nice, thank you. This seems to be a reasonable feature.

[danielebra]

Thanks @afrischk

@rcarriga anything else needed in order to merge?