fix: merge conflicting integration ID/name path into one path item

[eberle1080]

Problem

The API spec declared two separate path items that are identical except for the path-parameter name:

GET    /projects/{projectIdOrName}/integrations/{integrationIdOrName}   # getIntegration
DELETE /projects/{projectIdOrName}/integrations/{integrationId}          # deleteIntegration

Per the OpenAPI specification, two paths that differ only by parameter name are ambiguous and not allowed. Older versions of kin-openapi silently tolerated this, but v0.140.0 correctly rejects it:

invalid paths: conflicting paths
"/projects/{projectIdOrName}/integrations/{integrationId}" and
"/projects/{projectIdOrName}/integrations/{integrationIdOrName}"

This broke OpenAPI schema validation in server's builder-mcp openapi tools once kin-openapi was bumped to 0.140.0 (the builder-mcp/tools/operations test suite).

Fix

Merge both operations under a single path item keyed on {integrationIdOrName}.

This is also more accurate: both operations resolve identically on the server. DeleteIntegration uses GetIntegrationIdFromCtx, which accepts an ID or a name — confirmed by the passing TestDeleteIntegration_ByName test in server. So the delete parameter is renamed integrationId → integrationIdOrName and its description updated to "The integration ID or name."

Note on consumers

This changes the deleteIntegration path parameter name in generated SDKs (integrationId → integrationIdOrName). The actual route and behavior are unchanged.

🤖 Generated with Claude Code