Fixed detection of optional chains containing a reference

[Andarist]

fixes #56998

[Andarist]

I think an extra refactor should be made here.

isMatchingReference accepts reference as the first parameter but optionalChainContainsReference accepts it as the second one (!). That caused the issue here as both of them refer to both of the parameters as source and target - so it wasn't apparent that the reference (called a target here) is passed to isMatchingReference at the position that is used for candidate expressions (also called a target by that function).

I think it would make sense to:

1. rename those parameters to something like expression and reference or maybe candidate and reference. isMatchingReference sometimes calls recursively itself with adjusted source (what I propose to call a reference here) but I think that doesn't impact the proposed naming
2. use consistent order of parameters. I think what optionalChainContainsReference uses is better (reference passed as the second argument to it) but isMatchingReference is likely an older function so maybe the team would prefer that.