Add a test to verify resolver cache doesn't poison subsequent resolutions

[LalatenduMohanty]

Lets add a test to cover #766 [1] . We discussed this as part of #793 [2]

Adding a test to verify resolver cache doesn't poison subsequent resolutions.

    This test demonstrates the fix for issue #766 where the cache would
    store only candidates matching the first requirement's constraints,
    preventing subsequent less-constrained requirements from seeing
    newer versions.

    Scenario:
    1. First requirement: numpy<2 (e.g., from aotriton build dependency)
    2. Second requirement: numpy (e.g., from torch build dependency)

    Before the fix: Second resolution would incorrectly use numpy 1.26.4
    After the fix: Second resolution correctly uses numpy 2.2.0

[1] #766
[2] #793 (comment)