Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

feat: add @inlineArguments directive for cleaner resolver signatures

Implements the @inlineArguments directive which allows input object fields
to be expanded as inline arguments in GraphQL queries while bundling them
into a single parameter in resolver signatures.

This provides the best of both worlds:
- Clean, flat argument syntax for API consumers
- Simple, bundled parameter signatures for resolvers

Example:
  input SearchFilters @goModel(model: "map[string]any") {
    query: String
    category: String
  }

  type Query {
    search(filters: SearchFilters @inlineArguments): [Result!]!
  }

Clients use flat syntax: search(query: "test", category: "books")
Resolvers receive bundled param: Search(ctx, filters map[string]any)

Implementation:
- Schema transformation in codegen/inline_arguments.go
- Runtime schema expansion in generated code templates
- Resolver bundling logic in codegen/field.go
- Schema embedding in codegen/data.go

Test Coverage (11 integration tests + 2 unit tests):
- Flat vs wrapped argument syntax
- Partial and no arguments
- Required vs optional fields
- Default values on inlined arguments
- Mixed inline + regular arguments
- Schema reuse (same input type, multiple fields)
- Mutations with inlined arguments
- Directive preservation (@deprecated on fields)
- Introspection verification
- Error handling and validation

Closes #3884