After a consistency error occurs, `Reload metadata` button does not resolve the error

### Version Information

Server Version:v2.35.1 (Arm64V8)
CLI Version (for CLI related issue):v2.35.1 (Arm64V8)

### Environment

OSS

### What is the current behaviour?

After a consistency error occurs and the tables are correctly registered, executing the metadata reload button in the Hasura Console still leaves the consistency error displayed.

### What is the expected behaviour?

The metadata reload button will resolve the consistency error.

### How to reproduce the issue?

1. Use Docker on a Mac to launch a postgres database and Hasura Graphql Engine. Prepare metadata and application databases in postgres.
2. Launch another set of postgres database and Hasura Graphql Engine separately. I used AWS ECS Fargate to launch the Hasura Graphql Engine and configured it to use RDS's Aurora postgres database.
3. On the Mac, use Hasura CLI to launch the hasura console.
4. Create two tables and a relation between them.
5. Execute the following commands in order:
```
hasura metadata apply --endpoint --admin-secret
hasura migrate apply --endpoint --admin-secret --all-databases
```
6. Open the Hasura Console for the Hasura Graphql Engine created in step 2.
7. Consistency error will be displayed. This is the correct behavior since the migration was executed after applying metadata.
8. Press the `Reload metadata` button on the screen.
9. The consistency error remains. Since the correct tables are registered due to the migration, I expect that pressing the `Reload metadata` button will resolve the consistency error.

### Screenshots or Screencast


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

### Any possible solutions/workarounds you're aware of?

When you check `Reload all databases` and then press the `Reload metadata` button, the consistency error is resolved.

### Keywords

consistency error, reload all databases