Fix poetry with git dependencies

[jaysonsantos]

Hey there, this PR is to fix problems when you use poetry and git dependencies.
By default, poetry will generate a requirements.txt with -e/--editable flag which does not work well with -t (--target). This PR will read that file and rewrite the lines to make sure pip won't try to install in a wrong way.

[jaysonsantos]

The tests break because they try to clone the public repository using ssh and there is no key there.
What do you think is the best way to fix it? The fix I sent is actually to fix that problem.

[dschep]

@jaysonsantos any reason to not clone the public repository via https?

[jaysonsantos]

@dschep There is when the bug happens, which is a common way when using private repositories to avoid having passwords on the lock.

[tpansino]

@jaysonsantos This also fails if you connect over https as @dschep suggests, and wouldn't require an SSH key to be set up.

What do you think of using this instead?

bottle = {git = "https://github.com/bottlepy/bottle.git", tag = "0.12.16"}

Looking at the poetry export code, this should test out the same pathway you want.

I would very much like to see this PR merged, it's very annoying to try to use poetry and this plugin with any private or GitHub-hosted packages currently.

[dschep]

could you also resolve the conflicts please? This seems like a good PR to merge before i release next week :)

[tpansino]

@dschep @jaysonsantos If it's ok with you I'd be happy to make the requested changes and fix the merge conflict today. I just need to be granted contributor access.

[dschep]

@tpansino, that actually won't do it since this PR is from a fork. I can't actually commit my suggestions either. Feel free to make a new PR that's based on this one instead.

[jaysonsantos]

Closing this as #390 got merged