Fix UUID calibration with multiple branch tracking

What does this MR do and why?

Fix UUID calibration with multiple branch tracking

Multiple branch tracking could match findings from a different context and overwrite UUIDs, breaking calibration consistency across branches.

Only same context matches now override uuid, while cross context matches only reuse context_unaware_uuid.

This preserves deduplication without corrupting branch-specific UUIDs.

Changelog: fixed EE: true

Merge request reports

Loading