Support: array type for Logical Model field (LogicalModelType)

### Is your proposal related to a problem?

Currently, when you toggle "array" input (or set array as type) for respective Logical Model field, it gives you the following error
```
Arrays of scalar types are not currently implemented
```

### Describe the solution you'd like

Implementation of "array" type for [LogicalModelType](https://hasura.io/docs/latest/api-reference/syntax-defs/#logicalmodeltype)

### The metadata API ref for untracking and tracking LM
```json
{
"resource_version": 150,
"type": "bulk_atomic",
"args": [
{
"type": "postgres_untrack_logical_model",
"args": { "source": "default", "name": "album_tracks" }
},
{
"type": "postgres_track_logical_model",
"args": {
"source": "default",
"name": "album_tracks",
"fields": [
{
"name": "album_title",
"type": { "scalar": "varchar", "nullable": true }
},
{
"name": "track_name",
"type": { "array": { "scalar": "varchar", "nullable": true } }
}
]
}
}
]
}
```

### Screenshot

Start by tracing LogicalModelType and the postgres_track_logical_model metadata operation described in the issue, including how the existing scalar field type is handled. Done means an array field such as {"array":{"scalar":"varchar","nullable":true}} can be tracked without the current scalar-array error and behaves correctly.

Written by the indexing model from the issue text.