Fix: Where clauses with named arguments may cause generation of unintended queries

[emregullu]

• Do only one thing
• Non breaking API changes
• Tested

What did this pull request do?

During the building of Where clauses, the NamedExpr type is omitted while determining whether the expression should be wrapped in parentheses. Therefore, although it is required, Where clauses containing both named arguments and OR conditions are not wrapped, and this causes the generation of different queries than desired. This pull request tries to fix this issue.

User Case Description

eg:

For the gorm statement below,

db.Model(&User{}).Where("role = @role1 OR role = @role2",
map[string]interface{}{"role1": "admin", "role2": "super_admin"}).Find(&results)

the following query is generated.

SELECT * FROM users WHERE role = 'admin' or role = 'super_admin' AND users.deleted_at IS NULL

Due to the precedence of AND over OR, the query will be interpreted like

`WHERE role = 'admin' or (role = 'super_admin' AND users.deleted_at IS NULL)` 

instead of

`WHERE (role = 'admin' or role = 'super_admin') AND users.deleted_at IS NULL` 

which is actually intended, and it leads to getting softly deleted admin users without being aware, which may also be dangerous.

[sryavuz]

Thank you for the catch, LGTM 👍