refactor(app): ensure proper API cal data is associated to protocol labware

[mcous]

overview

This PR follows up on an #6100 and #6246. A given labware used in a protocol should be associated to a given entry in the labware calibrations results if the labware's:

1. loadName matches the calibration data entry, and
2. namespace matches the calibration data entry, and
3. version matches the calibration data entry, and
4. parent module (or lack of parent) matches the data entry

The implementation I wrote in #6100 was buggy, and #6246 noted that it resulted in incorrect quantities being displayed in the table. However, it it turns out 6100 was buggy for both quantity linking and calibration data linking. If a labware does not have a module parent, it could get linked (in UI) to module-based calibration data if the module-based calibration entry was earlier in the response array.

This PR adds a test and fix for this case.

changelog

• refactor(app): ensure proper API cal data is associated to protocol labware

review requests

• Tests look good
• Cal data gets linked in UI properly
• Quantity fixes from fix(app): don't doublecount labware on modules #6246 aren't messed up

risk assessment

Low. Unit test coverage was already high for this logic, and bug+fix was TDD'd.

[b-cooper]

🎲

[amitlissack]

Code looks good to me.