Improve --exclude-newer hints

[charliermarsh]

Summary

We now show a hint if there's an available version that's excluded and would satisfy the range (and include that version in the hint). Previously, we only showed this if all versions were omitted.

For example:

  × No solution found when resolving dependencies:
  ╰─▶ Because there are no versions of iniconfig and iniconfig==2.0.0 was published after the exclude newer time, we can conclude that all versions of iniconfig cannot be used.
      And because your project depends on iniconfig, we can conclude that your project's requirements are unsatisfiable.

      hint: `iniconfig` was filtered by `exclude-newer` to only include packages uploaded before 2006-12-02T02:07:43Z. The latest version satisfying the requirement is v2.0.0, published on 2023-01-07. Consider using `exclude-newer-
  package` to override the cutoff for this package.

Closes #18220.

[charliermarsh]

This ensures that when we determine the "latest available version", we still filter to make the test deterministic.

[mschoettle]

I just ran into an issue where exclude-newer is set to 7 days but pyproject.toml was updated by Renovate (forgot to configure minimum release age for it) to a ruff version that was released outside that range.

I got this error message and it took me some digging to figure out exclude-newer was the cause:

$ uv lock
  × No solution found when resolving dependencies for split (markers: python_full_version == '3.13.13' and sys_platform ==
  │ 'win32'):
  ╰─▶ Because there is no version of ruff==0.15.9 and admin:dev depends on ruff==0.15.9, we can conclude that admin:dev's
      requirements are unsatisfiable.
      And because your project requires admin:dev, we can conclude that your project's requirements are unsatisfiable.

      hint: The resolution failed for an environment that is not the current one, consider limiting the environments with
      `tool.uv.environments`.

Does this PR address this problem or is that a separate issue?

[charliermarsh]

Yeah I believe it would tell you that in the hint.

[nsoranzo]

@mschoettle See also the related #18914 issue.

[charliermarsh]

The complexity here is that we want to figure out which (excluded) version matches the resolver specifiers for that package. But the ExcludeNewer incompatibilities cause us to exclude the exact versions we care about! So we have to remove those incompatibilities from the tree.