Fix disambiguate all incorrectly affectly records

[realVinayak]

Fixes # My issue when doing conversion work

The problem in the previous code is you could have something like

Here, test1 has duplicates. So, if you click on the test1 on the top row and click disambiguate and perform "Apply All", it incorrectly chose rows just based on the key. Then, it applied the disambiguation to the same mapping path as the one currently active. So, it will apply a disambiguation on the second row with the mapping path of the first one, which is incorrect as test2 will be incorrectly disambiguated as test1.

This leads to backend always choosing test1 for test2. Seems like backend should have logic for not looking at disambiguation when a single match. I don't know use cases for multiple disambiguations for the same record in a single row -- I just tried making the code as semantically same as before. Could get rid of that to just do on all disambiguations in a single row.

I'll defer this PR to 7.9.5 when workbench is in react but opening it right now because this was annoying bug for conversion work. In my case, it led to uniqueness rule exception (a very confusing one) because everything seemed fine on the surface.

Checklist

• Self-review the PR after opening it to make sure the changes look good
  and self-explanatory (or properly documented)
• Add automated tests
• Add relevant issue to release milestone

Testing instructions

[maxpatiiuk]

This looks good, but pinging @sharadsw as he is doing a major workbench refactor this now in #4637

any changes we make to the workbench source code in the meanwhile may cause merge conflicts, and would have to be incorporated into the new refactored code

[grantfitzsimmons]

Seems like an incredibly urgent issue based on the description. @CarolineDenis What do you think?

[sharadsw]

This will cause a merge conflict with #4637 no matter what order we merge both PRs in. I think since this only changes one file and it's urgent, we can go ahead and merge this first. Shouldn't be difficult to resolve the conflict when it happens

[realVinayak]

wouldn't be suprised if there is bad data out there bc of this. we caught it now just bc of business rules (other cases where no business rules will not have been caught)

[grantfitzsimmons]

@CarolineDenis failing tests 😢