Fix minor CI issues

[AndydeCleyre]

. . . so we can focus on more important issues.

• Temporarily ignore issues Files included relatively in requirements.in file gets converted to absolute paths #2131 and pip-compile errors when generating hashes with AttributeError 'cache_clear' with pip v25.1 #2176 (and any other pip 25.1 issues)

  This is in order to see other tests all pass in CI during the PR review.
  I suggest dropping this commit before the PR is merged.

• Stop expecting these to be specially ignored: setuptools, wheel, distribute now covered by 8d5e46e

  See: Test failure: pip freeze no longer protects setuptools, distribute or wheel on Python 3.12+ #2104

• Use --strip-extras to suppress irrelevant warning for test_all_no_emit_options

• Accept complaint of any missing key in a known invalid pyproject.toml now covered by c8fb33a

  The stderr may stop after noting the missing version,
  without mentioning the missing name

• Introduce compatibility with click>=8.2, maintaining compatibility with <8.2

• Update test pkg: fake_with_deps

  • The version range for pyzmq was bumped for compatibility with newer ecosystem
  • The format was changed to a pyproject.toml, addressing this warning:

  DEPRECATION: Building 'fake_with_deps' using the legacy setup.py bdist_wheel mechanism,
  which will be removed in a future version.
  pip 25.3 will enforce this behaviour change.
  A possible replacement is to use the standardized build interface
  by setting the --use-pep517 option,
  (possibly combined with --no-build-isolation),
  or adding a pyproject.toml file to the source tree of 'fake_with_deps'.
  Discussion can be found at Deprecate legacy setup.py bdist_wheel mechanism for building projects pypa/pip#6334

  The rest of the test packages may be updated accordingly in the future.

Contributor checklist

• Included tests for the changes. (No new tests. The aim is to get existing ones passing in CI.)
• 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).

[webknjaz]

@AndydeCleyre so just a quick comment. I haven't yet looked into the diff, still en route home from the US.

@sirosen had a plan to have a stack of PRs to fix the CI. We're still in post-PyCon travels and may need a minute to regain mental capacity and decompress after so many days of intense interactions. I'll let him decide whether to pick commits from here. We already had a CI / infra fixing plan having met in person and did a lot of brainstorming over the sprints.

Let's not get into trying to repeat the same effort over the next week or two? Would that be okay with you?

[AndydeCleyre]

Sure, and thanks for working on this. Maybe this will be useful as a reference for some bit, if not for cannibalization.

[sirosen]

Yes to both of the above messages! Your effort and work on this is very much appreciated, and I plan to either cherry-pick directly or create co-authored commits.

But I have another full day of travel and will probably not get to look at this properly until Monday at the earliest.

Everyone's help pitching in on this problem is great to see! 🙂

[sirosen]

I just created #2184 with a cherry-pick from here. I'm trying to give credit where it's due and be very transparent.

I think most of these fixes are good, but should be part of adding support for Python 3.12+ or support for newer pip versions. I'd like to handle that next phase by moving forward the pipsupported versions and incorporating fixes (from here and possibly elsewhere). And I'd like to add Python 3.12 to the CI matrix. So I intend to inch the infrastructure forward and cherry-pick more from here, assuming that sounds good to everyone.

[webknjaz]

@AndydeCleyre could you rebase so we could see what's remaining unmerged?

[AndydeCleyre]

Sure, it's now rebased, and I've crossed out the two obsolete items from the original description.