perf: Assume internally created schemas as valid

[aarne]

Description

Sets assumeValid to true when creating new GraphqlSchema in stitchSchemas.

Im not 100% sure if this is really safe to do so, but the perf implications are non negligible. So if we cannot just assume the schema to be valid at this stage then we can hopefully at least leave this for the user to decide somehow?

Type of change

• [x] Performance improvement

How Has This Been Tested?

Internal releases.

Test Environment:

• NodeJS:

Checklist:

• [ ] 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 and linter rules pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: d10ed7bc500515069afcb296862fd0e312f12d6c

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

This PR includes changesets to release 3 packages

| Name | Type | | ------------------------- | ----- | | @graphql-tools/stitch | Minor | | @graphql-tools/federation | Patch | | federation-benchmark | 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

[ardatan]

Thanks!