Reloading remote schema does not pick up newly added enum values

### Version Information

Server Version: v2.23.0
CLI Version (for CLI related issue): v2.23.0

### Environment

EE

### What is the current behaviour?

I've observed that the [`hasura metadata reload`](https://hasura.io/docs/latest/hasura-cli/commands/hasura_metadata_reload/) CLI does not pick up on newly added enum values in remote schemas.

### What is the expected behaviour?

The expected behavior is for `reload` to pick up on new enum values.

### How to reproduce the issue?

1. Add a new enum value to a remote schema
2. Restart the remote schema w/ its new SDL
3. Run the `hasura metadata reload` command
4. Observe no changes to `remote_schemas.yaml`

### Screenshots or Screencast

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

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

The workaround is to go into the Remote Schema's Permissions tab, modify the permissions (e.g., uncheck some random input or type) and save, and then re-modify the permissions (re-checking what you previously unchecked).

### Keywords

Reload, reloading, remote schema, new enum value

Start with the `hasura metadata reload` command and reproduce the steps against a remote schema with a newly added enum value. Compare the remote schema SDL with `remote_schemas.yaml`; the work is done when reload records the new enum values without requiring permission changes.

Written by the indexing model from the issue text.