Introspect command does not pick up table column renames

### Component

This issue pertains to:
CLI -> c/v3-cli
Postgres (for issues that clearly relates to Postgres SQL execution) -> c/v3-ndc-postgres

### What is the current behaviour?

1. Rename a column in your table in pgsql
2. Run `ddn connector introspect sivvy_neon`
3. Run `model add`, `command add`, `relationship add` commands.

Observe that renamed column name is still listed as previous column name.

As a result running `supergraph build local` or `build create` will throw an error similar to this:

`ERR Code=opendds-validation Message="invalid metadata: error building schema: invalid metadata: unknown target column name status for field status in object type InsertProvidersObject (in subgraph app)"`

### What is the expected behaviour?

Expected behavior would be that columns that are renamed are picked up in the introspect command, and updated throughout following commands.

### How to reproduce the issue?

1. Spinup a hasura ddn -> pgsql connector
2. Generate a table, generate some columns
3. Run through introspect command
4. Rename a column in the table
5. Run introspect command again
6. Notice issue

### Screenshots or Screencast

N/A

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

Error log provided above.

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

Manually updating the renamed column in the `.hml` files in metadata seems to bypass this issue.

### Keywords

'rename', 'pgsql rename column'

Reproduce the problem with a Postgres connector using `ddn connector introspect`, then inspect the c/v3-cli introspection entry point and the follow-up `model add`, `command add`, and `relationship add` commands. Done means a renamed column is reflected after the second introspection and `supergraph build local` or `build create` no longer reports the old target column name.

Written by the indexing model from the issue text.