Add a check for pending graphql generated items

[FelixMalfait]

Problem: people forget to run npx nx run twenty-front:graphql:generate and npx nx run twenty-front:graphql:generate --configuration=metadata. So sometimes their changes will end up in a subsequent unrelated PR

We had a similar problem for TypeORM which we solved elegantly: https://github.com/twentyhq/twenty/blob/main/.github/workflows/ci-server.yaml#L82

We should do the same for graphql generation

[yadavshubham01]

Hey @FelixMalfait , should I try working on this issue?

[yadavshubham01]

@FelixMalfait Let me tell you how i approach this issue :-
I'm adding an automated check in the CI pipeline to ensure no uncommitted changes are introduced. This involves creating a script that runs the necessary GraphQL generation commands (npx nx run twenty-front:graphql:generate and npx nx run twenty-front:graphql:generate --configuration=metadata) and then verifies if any files have uncommitted changes. If changes are detected, the CI process will fail, prompting the developer to regenerate and commit the updates. This approach is similar to how we handled the TypeORM issue and ensures consistency while preventing unrelated changes in future PRs