[3.1.1] Query: Don't use VisitAndConvert in projectionBindingExpressionVisitor

[smitpatel]

Since visiting inner could return null

Resolves #18888

[ajcvickers]

Removing servicing consider this morning since we don't have the template done yet.

[smitpatel]

Description
In new query pipeline, we were using ExpressionVisitor.VisitAndConvert function in certain places. The function throws exception if Visit returned null expression. In 2 specific visitor we return null if we fail to translate something to SQL so that we can throw better exception or client eval the projection. But usage of VisitAndConvert ended up throwing early and useless exception message.

Customer Impact
Query failure when query involves DTO construction with parameter in projection.

How found
Customer-reported (#18888)

Test coverage
We did not have test coverage where DTO took parameter in ctor.

Regression?
Yes, from 2.2.

Risk
Small. Instead of using VisitAndConvert, we call Visit only and not throw any exception if null returned. It is same as underlying code of VisitAndConvert except exception throwing mechanism.

[smitpatel]

@ajcvickers - filled it.

[ajcvickers]

@smitpatel This is approved for 3.1.1 servicing. Please merge ASAP.

[jamshedd]

Approved for 3.1.1