Error applying migrations on a Hasura Instance

### Version Information

Server Version: 2.0.0-alpha.4
CLI Version (for CLI related issue): 2.1.0-beta.3

### Environment

OSS

### What is the current behaviour?

While applying migrations on the default database, it throws the following error -
```
ERRO skipping applying migrations on database default, encountered:
{
"internal": "no connection to the server\n",
"path": "$",
"error": "connection error",
"code": "postgres-error"
}
```
But the migration status command on the default database is working fine. Hasura console is also working fine, and I can view tables on the default database along with the data. But only when I try to apply the migrations, I get the above error, which is pretty weird. And it has happened for the first time, I have been running migrations on this instance before, without any issue.

### What is the expected behaviour?

Migrations should run on the default database.

Start by reproducing migration application on the default database and compare it with the working migration status command and Hasura console. Inspect the resulting connection error and migration behavior; done means migrations apply successfully to the default database without the reported no-connection error.

Written by the indexing model from the issue text.