Modifying remote schema with invalid metadata causes a console crash

### Version Information

Server Version: 2.15.1

### Environment
OSS /EE

### What is the current behaviour?

Have inconsistent metadata from a remote schema go to remote schemas in the console, then click Modify, get error
```Error
at r.e (https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.15/vendor.js.gz:1:9016578)
at rl (https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.15/vendor.js.gz:1:36568409)
at tl (https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.15/vendor.js.gz:1:36568202)
at Jc (https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.15/vendor.js.gz:1:36604056)
at Dc (https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.15/vendor.js.gz:1:36595705)
at Pc (https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.15/vendor.js.gz:1:36595630)
at Sc (https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.15/vendor.js.gz:1:36592480)
at https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.15/vendor.js.gz:1:36543452
at t.unstable_runWithPriority (https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.15/vendor.js.gz:1:36619263)
at oi (https://graphql-engine-cdn.hasura.io/console/assets/channel/stable/v2.15/vendor.js.gz:1:36543161)
```

### What is the expected behaviour?

No Error

Start by reproducing the crash in the console: use inconsistent metadata from a remote schema, open Remote Schemas, and click Modify. The payload names no source files or tests; done means the Modify flow no longer throws an error for this metadata.

Written by the indexing model from the issue text.