Schema introspection query failed {"errors":[{"message":"Application update required"}]}

### Version Information

Server Version: v2.12.0

### Environment

Docker, hasura/graphql-engine:v2.12.0

### What is the current behaviour?

When I try to use an authorization header in the console and click the "Decode JWT" button I get redirected to an error page with the below error. The console also complains: `Schema introspection query failed {"errors":[{"message":"Application update required"}]}` Nothing of use is printed to the container logs.

### What is the expected behaviour?

To be able to use the console without the `X-Hasura-Admin-Secret` header to test queries as a user.

### How to reproduce the issue?

1. Uncheck the checkbox next to the `X-Hasura-Admin-Secret` header
2. Add an `Authorization` header with the value `Bearer [valid JWT here]`
3. Click the `Decode JWT` button on the right

### Screenshots or Screencast


### Please provide any traces or logs that could help here.

```
e@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:2119848
e@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:2122624
e@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:2122723
rc@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25862835
tc@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25862628
Xl@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25898482
Hl@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25890133
Pl@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25890056
Cl@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25886906
ui/<@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25837878
t.unstable_runWithPriority@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25913689
oi@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25837587
ui@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25837825
si@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25837758
El@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25883658
enqueueSetState@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25841611
_.prototype.setState@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:25786527
e@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:2112018
e/<@https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.12/vendor.js.gz:1:2112378
```

### Any possible solutions?

Don't know.

### Can you identify the location in the source code where the problem exists?

No.

### If the bug is confirmed, would you be willing to submit a PR?

Don't know the source code well enough.