feat(manager/poetry): Support tag as git-dependency on github

[yetanotherion]

Changes

Parse git dependencies like

{git = "https://github.com/tiangolo/fastapi.git", tag="1.2.3"}

or

{git = "git@github.com:tiangolo/fastapi.git", tag="1.2.3"}

and support them as github-tags datasources.

Context

GitHub Packages currently lacks support for PyPI repositories. As an alternative, some companies opt to use git-dependencies for hosting internal dependencies rather than installing third-party solutions such as artifactory or Google’s Artifact Registry. This pull request adds support for specific use cases that rely on git tags, as discussed in issue #21848.

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[viceice]

please correctly fill the PR template

[yetanotherion]

Thanks viceice! If that's fine with you, I'll wait for rarkins's approval before merging.

[yetanotherion]

Thanks a lot rarkins!

[renovate-release]

🎉 This PR is included in version 35.70.0 🎉

The release is available on:

• GitHub release
• 35.70.0

Your semantic-release bot 📦🚀

[yetanotherion]

rarkins, viceci, just wanted to congratulate you on the process put in place in renovate.

Everything is so self explanatory that I don't even have to ask when the PR will be released:

• I have an automated comment that tells me so
• With the info in the releases of the related github-action, I can conclude that this feature will be available in the coming days in the github-action too.

So far, contributing to renovate has been the best experience I ever had working in an open source project 👏 👏 👏, thank you!

[gnuletik]

Hi, thanks for this PR!

In our projects, this does not seems to work on tags starting with a v prefix (e.g. v1.2.3).
We get the following error: WARN: Unexpected range error.

This seems to be a quite common behavior: https://semver.org/#is-v123-a-semantic-version

Is it an intended behavior?

Thanks!