Performance for upgrades checking

[dylant-da]

When checking modules individually for upgrade validity we re-run the following for each module:

• dependency validation
• topological sorting of dependencies
• populating list unchanged packages (this is no longer implemented but I'd like to add it back - refer to Add code for structural equality, check that keys are upgradeable (2.9.x) #19666 (comment))

It would be ideal if we could save a lot of effort on each module where possible. This will require a bit of rearchitecting of the upgrade checking logic.

[paulbrauner-da]

Also here, the filter could produce a lazy map that would only test as we iterate over the keys, since we return an error for the first one only.

[dylant-da]

This'll just be a general ticket in which we track perf issues