Hasura actions not available when defined as queries in relay

### Version Information

Server Version: v2.19.0
CLI Version (for CLI related issue): v2.15.2

### Environment

Gitpod/Hasura cloud

### What is the current behaviour?

### What is the expected behaviour?

When Hasura action is created as a query it doesn't appear in "Explorer" and we can't call this action by name either by writing action name directly in "GraphiQL"
Note: This issue only happens in relay, action that is created using "Query" is available in non-relay version of graphql but is not available in relay.

### How to reproduce the issue?

1. create a Hasura action using type Query
2. give permission to role using to access this query
3. turn on relay
4. in API explorer query explorer this action can't be queried

### Screenshots or Screencast

defination of action:

action non relay:

action in relay:

Possibly

My guess is that since we can't query any view or table where primary keys are not defined in relay. This might be related to that same issue

### Keywords

hasura action
query action

Reproduce the issue in Hasura Cloud or Gitpod using the listed steps, then compare the Relay and non-Relay API Explorer schemas and GraphiQL behavior for a query action. The fix is complete when a permitted query action appears in the Relay explorer and can be called by name.

Written by the indexing model from the issue text.