Console graphql engine check mix console api migration health and graphql-engine health

### Version Information

Server Version:
CLI Version (for CLI related issue):

v2.11.X -> v2.14.0.beta2

### Environment

OSS Edition

### What is the current behaviour?

When migration api is unavailable, console consider that graphql-engine is unavailable.

### What is the expected behaviour?

Data tab should be still available but all migration related stuffs should be disabled

### How to reproduce the issue?

1. ```docker run -p 127.0.0.1:8080:8080/tcp --volume /path/to/config.yaml:/config.yaml--entrypoint /bin/hasura-cli hasura/graphql-engine:v2.14.0-beta.1.cli-migrations-v3 console --console-port 8080 --address 0.0.0.0 --api-port 8081 --no-browser ```

2 Connect to browser

### Screenshots or Screencast


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

* We use console behind a vpn + reverse proxy which enforce security and user auth, maybe a flag --api-url is missing to specify external api url which is usable from front.
* Disable migration api related feature in console when this api is unavailable.
* Change error message to indicate that migration/console api is unavailable instead of displaying a message that indicate that graphql-engine is unavailable which is pretty confusing.

### Keywords

console, proxy

Start by reproducing the issue with the provided Docker command and inspect the console's separate health checks for the migration API and graphql-engine. Done means the Data tab remains available when the migration API is unavailable, migration-related features are disabled, and the error identifies the unavailable service accurately.

Written by the indexing model from the issue text.