Filter out origin ireqs for extra requirements before writing output annotations

[chrysle]

Resolves #2003, closes #2007

Contributor checklist

• Included tests for the changes.
• PR title is short, clear, and ready to be included in the user-facing changelog.

Maintainer checklist

• Verified one of these labels is present: backwards incompatible, feature, enhancement, deprecation, bug, dependency, docs or skip-changelog as they determine changelog listing.
• Assign the PR to an existing or new milestone for the target version (following Semantic Versioning).

[AndydeCleyre]

Thanks!

Minor note on terms, in the pip-tools context: "header" usually refers to the big comment at the top, while the comments this PR affects are "annotations."

[chrysle]

Right, I don't know what moved me to replicating the mistake ;-)

[webknjaz]

Nit: in the future, use the pathlib interface of the tmp_path fixture.

Suggested change

	with open(req_in, "w") as req_out:
	req_out.write("package-with-extras[extra1,extra2]")
	req_in.write_text("package-with-extras[extra1,extra2]", encoding="utf-8")

[chrysle]

Thanks for the hint!

[lociii]

@atugushev When do you expect a new release of pip-tools that includes this compatibility fix?
There are situations (e.g. we're using renovate with pip-tools) where you cannot downgrade pip and run into this issue.

[jonesbusy]

There are situations (e.g. we're using renovate with pip-tools) where you cannot downgrade pip and run into this issue.

Same situation here.

Solution I found is to rollback pip3 directly on renovate container (if you are using self hosted)

install-tool python 3.10.13
pip3 install --upgrade pip==23.2.1