Why does hasura have basically no support for postgresql arrays?

### Is your proposal related to a problem?
I'm frustrated when arrays aren't first class citizens in Hasura. To insert values into an array such as `text[]`, I seem to have to format a stringified array in sql format such as `"{\"/tmp/lunatrace130366288/package-lock.json\"}"`. Operators for array comparison such as `@>` seem to be totally inaccessible from graphql. Why is Hasura so clunky with arrays?
### Describe the solution you'd like
I'd like arrays to work properly and be part of the overall system. Arrays often ARE the right abstraction in a relational database. Some people will say "you should never use arrays" but I think they do not understand the tradeoffs and when it is appropriate.

No files, tests, or entry points are named in the issue. Start by clarifying the intended PostgreSQL array input and comparison-operator behavior in the GraphQL API; done would require an agreed scope and corresponding coverage for insertion and array operators.

Written by the indexing model from the issue text.