chore(deps): update @graphql-codegen dependencies

[kumimaru2002]

🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.

Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.

Description

This PR updates outdated packages in the @graphql-codegen/near-operation-file-preset to their latest versions. The update aims to ensure compatibility and access to the latest features and improvements, thereby maintaining the overall stability and security of the project.

Related #772

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Screenshots/Sandbox (if appropriate/relevant):

codesandbox

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

yaml test

Test Environment:

• OS: 13.3
• "@graphql-codegen/add": "^5.0.3"
• "@graphql-codegen/plugin-helpers": "^5.0.4"
• "@graphql-codegen/visitor-plugin-common": "^5.3.1"
• "@graphql-tools/utils": "^10.3.1"
• "@graphql-codegen/cli": "^5.0.2"
• NodeJS: v18.16.0

Checklist:

• [x] I have followed the CONTRIBUTING doc and the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: b0c5e5f580964ff094b8fe64fa0458860db31e75

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@graphql-codegen/near-operation-file-preset	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[kumimaru2002]

Sorry. After resolving the conflict in yarn.lock, I unintentionally did a force push. Please review it again.

[kumimaru2002]

I have resolved the conflicts in the yarn.lock file. Fixing conflicts in the yarn.lock file is quite troublesome, so I would appreciate it if you could merge it as soon as possible.

[kumimaru2002]

@dotansimha I would appreciate it if you could review it.

[DanieleFedeli]

Hey hey, what's blocking this? Can I help somehow? @dotansimha

[amakhrov]

Related older PR from Renovate (abandoned): https://github.com/dotansimha/graphql-code-generator-community/pull/609

Is there a way to proceed with either of the PRs?