Make it even easier to add support for custom GF fields

[justlevine]

Is your feature request related to a problem? Please describe.

People choose Gravity Forms for its extensibility. While v0.10 made much progress to help devs support custom form fields, it still requires several filters to make work.

We should explore ways to make this even easier in WPGraphQL for GF, ideally by offering a single function that handles all the heavy lifting.

Describe the solution you'd like

In theory, a register_graphql_gf_form_field() function that resembles its namesake.

The function should let users

1. Define the necessary GraphQL fields on the autogenerated FormField object.
2. Define the FormFieldValueInput field for mutation support.
3. Let you overwrite the autogenerated FormField object type name.

Function arguments and usage should be as similar to core WPGraphQL register_graphql_{} functions as possible.

[justlevine]

Automated Triage

Classification: type: enhancement (existing) - priority: medium - status: needs discussion
Agent-feasible: Partially - the public API surface (function signature, argument shape) is clearly specified, but the internal registration flow it must hook into is complex enough that the design needs human sign-off before implementation.
Estimated effort: Agent high - Human medium

Summary: Proposes a single register_graphql_gf_form_field() helper that abstracts the multi-filter process of registering custom GF field types in the GraphQL schema, mirroring core WPGraphQL conventions. Well-specified on the "what"; the "how" intersects several existing registration paths (FormField object generation, FormFieldValueInput, type naming) and needs an architectural decision.

Next steps: Needs discussion on the registration flow before an agent can implement cleanly. Recommend the owner sketch the target signature and which existing filters get consolidated.