Incorrect json type narrowing in the presence of lists

Nobody has claimed this yet.

### Describe the bug

Unfolding of json fields with incompatible array and primitive types produces incorrect and inconsistent types.

Concretely, after syncing a table with a json column "my_column", with entries containing:
```json
{"field": [1]}
{"field": [2]}
{"field": 1}
{"field": 2}
```

sync will unfold `jsoncol -> field` and assign it a database_type/base_type pair of either `"text", :type/Array`, or `"decimal", :type/Integer`, depending on the order of the rows.

Both are wrong, and should be at best `"text", :type/Text`

### To Reproduce

Sync a table with a json field with values
```javascript
{"field": [1]}
{"field": [2]}
{"field": 1}
{"field": 2}
```

### Expected behavior

_No response_

### Logs

_No response_

### Information about your Metabase installation

```JSON
metabase v1.55
```

### Severity

P2

### Additional context

_No response_

Reproduce table sync with a JSON column containing both numeric arrays and numeric primitives under the same field. Trace JSON field unfolding and type inference for that field, then verify that incompatible array and primitive values consistently resolve to text/Text rather than depending on row order.

Written by the indexing model from the issue text.