Add Suave server integration package

[Copilot]

This adds an official Suave integration package for FSharp.Data.GraphQL, following the existing Giraffe/Oxpecker shape. The new package exposes GraphQL as a Suave WebPart so it can be embedded directly into larger Suave applications.

• New Suave integration package

  • adds FSharp.Data.GraphQL.Server.Suave
  • exposes:
    • HttpHandlers.graphQL
    • HttpHandlers.setRequestType
  • supports the existing server behaviors needed for:
    • GET introspection requests
    • POST JSON GraphQL requests
    • multipart upload requests

• Request handling model

  • maps Suave request data into the existing GraphQL execution flow instead of introducing a parallel server path
  • includes a Suave-specific IInputExecutionContext implementation for file uploads
  • preserves the existing Request-Type response header convention used by the current integrations

• Packaging and build wiring

  • adds the new project to solution files
  • includes the package in shared dependency management
  • wires pack/push targets into the build script alongside the other server integration packages

• Focused coverage

  • adds targeted tests for the Suave handler covering:
    • JSON query execution
    • GET introspection
    • multipart file upload execution

Example usage:

open Suave
open Suave.Operators
open FSharp.Data.GraphQL.Server.Suave

let app =
    HttpHandlers.setRequestType
    >=> HttpHandlers.graphQL Schema.executor rootFactory

[njlr]

@copilot Does this support websocket aspects of GraphQL spec?

[xperiandri]

@copilot Does this support websocket aspects of GraphQL spec?

@copilot answer, please.
Check the WebSockets implementation in ASP.NET Core project and can it be used or is it referenced by Suave support implementation and give an answer

[Copilot]

@copilot Does this support websocket aspects of GraphQL spec?

@copilot answer, please.
...

Checked this in the current implementation at 46c8871: no, the Suave package does not support the WebSocket/GraphQL-over-WebSocket part right now.

What exists today in FSharp.Data.GraphQL.Server.Suave is only HTTP handling for GET/POST in src/FSharp.Data.GraphQL.Server.Suave/HttpHandlers.fs. There is no WebSocket route, no socket accept flow, and no reference to the ASP.NET Core WebSocket middleware.

The WebSocket implementation lives in src/FSharp.Data.GraphQL.Server.AspNetCore/GraphQLWebsocketMiddleware.fs and is wired through UseWebSocketsForGraphQL in src/FSharp.Data.GraphQL.Server.AspNetCore/ServiceCollectionExtensions.fs. The Suave project does not reference FSharp.Data.GraphQL.Server.AspNetCore, so that middleware is not reused by the Suave integration.

So the short answer is: HTTP GraphQL is supported in Suave, WebSocket GraphQL is not. Reusing the ASP.NET Core implementation as-is would not work directly; it would need either a Suave-specific WebSocket adapter or a refactor that extracts the transport-agnostic parts into shared code.