feat: add type branding to graphql in TS outputs

[svidgen]

Description of changes

In order to brand the generated graphql for TypeScript, we need to know the underlying operation type (Query | Mutation | Subscription) and specific operation name (CreateBlog, ListBlogs, etc.) at the time the graphql is formatted for the language output. This PR:

1. Weaves op name and type through the statements map.
2. Derives relative types import path from config.
3. Conditionally adds types if the language is typescript.

Issue #, if available

Description of how you validated changes

1. Updated snapshot for new TS output (tests pass)
2. Ran through scenarios (To double-check functionality, these are combinations to replicate):

library	codegen	expected outcome
old	old	Base cases / no change	✅
old	new	Base cases / no change	✅
new	new	Base cases + API calls show specific arg and return types, preventing bad invocation	✅
new	old	Base cases + allows custom typing of both arguments and result	✅

Base cases

1. Untyped graphql has generic typing — API category cannot infer or enforce specifics
2. Overrides per the docs using GraphQLQuery and GraphQLSubscription wrappers provides return types

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)
• Breaking changes to existing customers are released behind a feature flag or major version update
• Changes are tested using sample applications for all relevant platforms (iOS/android/flutter/Javascript) that use the feature added/modified

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[svidgen]

Marking as draft again until PM's can review next Thursday. Happy to incorporate feedback between now and then though.