feat(manager/pipenv): Support custom environment variable usage in Pipfile source URLs

[fivetide]

Changes

This change expands functionality of pipenv to allow for arbitrary credential placeholders as outlined in discussion #26447.
In addition, multiple source-urls can now be handled.

Context

• Support custom environment variable usage in Pipfile source URLs #26447

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

[rarkins]

@fivetide thank you for this PR!

I found the logic flow a little hard to follow, and think this will be a little hard to maintain. I know you're mostly just extending the existing flow, but the additional complexity has now increased an existing problem of it being hard to understand.

Would you mind adding some comments to the flow so that it's easier to follow and for future maintainers? Sometimes improved variable names make commenting unnecessary too.

Once you're done with that, I'll see if there's anything I can add myself

[rarkins]

@fivetide it's best that you don't merge from main unless it's to fix something. Otherwise it resets the tests and I need to manually approve it again. If/when @viceice it will start automerging, assuming tests have passed

[fivetide]

Hey @rarkins, @viceice thanks for getting this PR ready. It looks to me that the merge is blocked by outdated changes. can you point me to how to resolve that?

outdated

[rarkins]

@fivetide it will now automerge once Michael approves

[fivetide]

Thanks a whole lot to you guys for helping me making this happen!

[renovate-release]

🎉 This PR is included in version 37.327.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀