feat(manager/pip_requirements): allow = as extra-url separator

[Finkregh]

See also: #29726

Changes

manager/pip_requirements

Before:

only --extra-index-url http... matched

After:

also --extra-index-url=http... matches

Context

These lines reflect CLI arguments, normal or expected behaviour is that --foo bar and --foo=bar lead to the same result.

This is not explicitly documented, but inferred from behaviour of many other tools: https://pip.pypa.io/en/stable/reference/requirements-file-format/

Documentation (please check one with an [x])

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

Please comment if the docs should be updated, and where.

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

[CLAassistant]

All committers have signed the CLA.

[Finkregh]

The CI seems to be stuck :( @rarkins

[rarkins]

GitHub requires manual approval of workflows any time a new contributor pushes to their branch. They're not stuck as in bug, but stuck as in security

[Finkregh]

I don't know how to fix the issues the CI is showing 🙈

[rarkins]

Focus on coverage first

[RahulGautamSingh]

Due to split on = the flags will be included in the registryUrl too
ie. for

--index-url=https://artifactory.company.com/artifactory/api/pypi/python/simple --trusted-host artifactory.company.com --default-timeout 600

registryUrl will be:
https://artifactory.company.com/artifactory/api/pypi/python/simple --trusted-host artifactory.company.com --default-timeout 600

whereas we want:
https://artifactory.company.com/artifactory/api/pypi/python/simple

This is also the cause of the failing tests in CI.

[Finkregh]

Ah, good point. I'll look into it as I find time.