SQLSelect — AddHaving passes wrong argument order

SQLSelect: correct AddHaving argument order
- Component: `src/ClassModules/SQLSelect.cls` (around 71–95)

### Problem
- Calls `SQLCondition.Create` with `(Field, op, Value)` but signature is `(Expression1, Expression2, Operator)`.

### Snippet (actual)
```vb
NewHaving.Create Field, op, Value
```

### Expected
```vb
NewHaving.Create Field, Value, op
```

### Steps to Reproduce
1) Add a HAVING with a non-default operator.

### Actual
- Generates the comparison with swapped operands/operator.

### Proposed Fix
- Pass `(Field, Value, op)` consistently in both branches.

---

Open src/ClassModules/SQLSelect.cls around lines 71–95 and inspect AddHaving in both branches, starting with the calls to SQLCondition.Create. Reproduce a HAVING using a non-default operator and verify that both branches generate the comparison with the expected argument order.

Written by the indexing model from the issue text.