Only compute `ClientSideBaseVisitor`'s `fragmentsGraph` once, at instantiation time

Description

As mentioned in https://github.com/dotansimha/graphql-code-generator/issues/10018, ClientSideBaseVisitor's fragmentsGraph is implemented as a getter, despite not depending on anything that changes after the class is first instantiated. Turning fragmentsGraph into a static property improved build time from ~130s to ~50s in a big monorepo.

This PR does that and it makes field fragmentsGraph depends on (_fragments) read-only to make sure we don't break the assumption behind pre-computing the former.

Related: #10018

Type of change

Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] 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):

Adding links to sandbox or providing screenshots can help us understand more about this PR and take action on it as appropriate

How Has This Been Tested?

Run codegen on a mid-sized project using client-preset and measure the build time
Make the change to only compute fragmentsGraph once per ClientSideBaseVisitor instance
Run codegen again and compare the build time

Test Environment:

OS: macOS
NodeJS: 18.18.2
graphql version: 16.2.0
@graphql-codegen/client-preset version(s): 4.2.6
@graphql-codegen/visitor-plugin-common version(s): 2.13.1

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
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] 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
[x] 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 detected

Latest commit: 049b7224d4a666132e63f84c64c413a8cfe7f899

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

This PR includes changesets to release 9 packages

| Name | Type | | ------------------------------------------ | ----- | | @graphql-codegen/visitor-plugin-common | Patch | | @graphql-codegen/typescript-document-nodes | Patch | | @graphql-codegen/gql-tag-operations | Patch | | @graphql-codegen/typescript-operations | Patch | | @graphql-codegen/typescript-resolvers | Patch | | @graphql-codegen/typed-document-node | Patch | | @graphql-codegen/typescript | Patch | | @graphql-codegen/graphql-modules-preset | Patch | | @graphql-codegen/client-preset | Patch |

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

dotansimha / graphql-code-generator