Allow relative paths when specifying local dependencies

• I am on the latest Poetry version.

• I have searched the issues of this repo and believe that this is not a duplicate.

• OS version: Ubuntu 20.04.6 LTS
• Poetry (version 2.1.2)
• Python version: 3.10

Issue:

Sort of a follow up to https://github.com/python-poetry/poetry-plugin-export/issues/145

my pyproject.toml file specifies a local dependency:

[tool.poetry.dependencies]
my_pkg = {path = "../../../my_pkg", develop=true}

The poetry.lock file specifies my_package with a relative path, which is correct.

But running poetry export --output requirments.txt results in

# requirements.txt
-e file:///full/path/to/my/local/dependency/my_pkg; 

this requirement.txt becomes unusable in CI due to the absolute path. There should be an optional to make the path in requirements.txt local path instead.

Start by reproducing the poetry export --output requirements.txt command with a local dependency declared by a relative path. Inspect the export handling for path dependencies and determine how an optional setting could preserve relative paths; done means the generated requirements file uses a usable local path for CI. Run the relevant export checks after identifying them.