Move tool detection to renovatebot/detect-tools

[rarkins]

Describe the proposed change(s).

We should move tool detection to a separate repo/module so that it can be shared outside Renovate, particularly with some Containerbase tooling we are building.

Start with Poetry and Pipenv.

Example from: https://github.com/renovatebot/renovate/blob/main/lib/modules/manager/pipenv/artifacts.ts

Instead of a getPythonConstraint() function where we pass content to the function, we should instead call our new external library and pass it a fully qualified path/directory.

[renovate-release]

🎉 This issue has been resolved in version 38.39.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 38.39.0

Your semantic-release bot 📦🚀

[viceice]

we only fixed a single manager

[zharinov]

we only fixed a single manager

I don't like how its scope is unclear, while refactoring each of the remaining managers seems to be quite laborous. Let's close this one and create new ones on per-manager basis.

[viceice]

why not using this as the meta issue with a to-do list of sub issues? so we've an overview.

[zharinov]

Because I feel more satisfied when PR closes the issue rather than just checking the box 🙂

[viceice]

that's why I suggest to have an uber issue and then create an issue for each manager listed as task list inside the uber issue

[zharinov]

Here we go, I just created tracking issue