Some `where` property comparisons do not create a `QueryParameter`

[JordanMarr]

Property = comparisons all use KataUtils.getQueryParameterForValue function which checks for generated ProviderDbType attributes and then wraps the query parameter value in a QueryParameter type. This approach is good because it allows the query parameter to use the actual database column type instead of inferring a less specific column type.

The LinqExpressionVisitor is responsible for parsing the query expressions and creating where clause parameters.

Case where conditions that are not wrapping parameter values:

• like / =% / notLike / <>%.*

[JordanMarr]

Tried to wrap this parameter in a QueryParameter causes SqlKata to fail. Closing becase a LIKE query is going to trigger a table scan anyway, so the parameter type shouldn't matter here.