Deprecate usage of /v1/query for console data fetching

### Is your proposal related to a problem?

When browsing data from the console data tab, the `/v1/query` api is used to fetch and update rows.

This is a problem as this api is undocumented, which can be confusing. The endpoint is also documented as being deprecated.

**Note** this is not about the use of `run_sql` used for things like fetching information on database structure. That uses the `/v2/query` api.

### Describe the solution you'd like

The use of the api should be deprecated and the graphql api used instead.

### Describe alternatives you've considered

If these APIs are to be used in the long term, they should be documented.

#8997 proposes the opposite approach: document these APIs and make them official.

Start by locating the console data tab code that fetches and updates rows through /v1/query, then compare the available GraphQL API path. Done means the console no longer uses /v1/query for those operations; resolve the relationship with #8997 before proceeding.

Written by the indexing model from the issue text.