Automatically handle storing insert/update/delete of rows in an enum table

### Is your proposal related to a problem?

When refreshing the migration from scratch it is troublesome to insert all the rows in an enum table by hand. As far as I know, there is no official solution to this problem yet. A similar [issue](https://github.com/hasura/graphql-engine/issues/3142) from the past has been closed.

### Describe the solution you'd like

It would be great if Hasura had a functionality that could automatically handle storing insert/update/delete of rows in an enum table. I understand if this feature request is too complicated, please let me know as well.

### Describe alternatives you've considered

- I have considered the alternative provided in this [comment](https://github.com/hasura/graphql-engine/issues/3142#issuecomment-1063054632).
- I have considered [seed data migration](https://hasura.io/docs/latest/graphql/core/migrations/advanced/seed-data-migration/).

### If the feature is approved, would you be willing to submit a PR?

Start with the seed data migration documentation and the prior issue and comment linked in the proposal. Define how enum-table insert, update, and delete changes should be represented when migrations are refreshed from scratch. Done means the behavior and scope are agreed, with migration examples or tests that cover the proposed workflow.

Written by the indexing model from the issue text.