[Console] Modifying an inconsistent remote schema redirects to the 404 page

### Version Information

Server Version: 2.1.1

### What is the expected behaviour?

I should be able to modify or remove an inconsistent remote schema.

### What is the current behaviour?

When faced with an inconsistent remote schema (for example the remote URL changed), users are completely unable to modify or remove it through the web console.

### How to reproduce the issue?

1. Using `allow_inconsistent_metadata: true` in the metadata, add an invalid remote schema URL through the API's `replace_metadata`
2. In the console, you can't modify the remote schema (takes you to a 404 immediately)

Alternatively, correctly create a remote schema with a given URL. Then from that remote schema, change the API URL. Hasura will deem the remote schema inconsistent and you can't modify the URL.

### Screenshots or Screencast



Interestingly, the experimental feature "remote schema permissions" doesn't freak out as much.