Ruby: Avoid a forced CP.

[alexet]

The disjunction mentions request on one side and requestNode on the other. This means that the disjunction can't go first and the call the the charpred must be done first. Due to a inline_late bindingset[...] call inside the inlined new.getReturn(_) we can't start with that inside the disjunct and we therefore must choose a CP. Luckily in most databases the CP ends up small.

This is not important at all for the new join orderer as better heuristics now means it picks the correct CP but I felt it was better to avoid it in case someone creates a project with many Net::HTTP.new(...).get(...) calls.