Pass extra when evaluating lockfile markers

[charliermarsh]

Summary

When we serialize and deserialize the lockfile, we remove the conflict markers. So in the linked case, the edges for the tqdm entries are like:

complexified_marker: UniversalMarker {
    pep508_marker: python_full_version >= '3.9.0',
    conflict_marker: true,
},

However... when we evaluate in-memory, the conflict markers are still there...

complexified_marker: UniversalMarker {
    pep508_marker: true,
    conflict_marker: extra == 't1' and extra != 't2',
},

So if uv run creates the lockfile, we evaluate this as false.

We should make this consistent, and I expect @BurntSushi is aware. But for now, it's reasonable / correct to pass the extra when evaluating at this specific point, since we know the dependency was enabled by the marker.

Closes #9533 (comment).

[BurntSushi]

Yeah I think this makes sense. In #9370, the call site here is indeed changed. But it passes all activated extras.