[Testing utilities] Create separate entrypoint for new testing utilities

[alessbell]

Issue Description

The new testing utilities will have at least a couple of peer dependencies.

For now, we'll advise users to install them in the docs. If we export the new testing utilities that import these peer dependencies in our regular .cjs testing entrypoint, other users will see an error if they're not installed.

If we make these explicit dependencies, all our users will download them whether or not they're using the new testing utilities, so I proposed a few options and discussed with @phryneas and for now we'll opt for a separate entrypoint.

Link to Reproduction

N/A

Reproduction Steps

No response

@apollo/client version

N/A

[alessbell]

Thoughts on the entrypoint name @phryneas @jerelmiller? Should it be feature-specific (testSchema/createTestSchema) or something like alpha-testing?

Edit: went with testing/alpha for now

[alessbell]

Closed via #11783

[github-actions]

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo Client usage and allow us to serve you better.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
For general questions, we recommend using StackOverflow or our discord server.