consume any-sdk v0.5.5-alpha01: OCI doc-level env vars, body coercion, snake/wire parity wire-through (#705, #726, #725, #710) - #731

Consumes any-sdk v0.5.5-alpha01 (dc7bad2) and lands the three stackql-side wire-through items that release needs, with robot coverage for all seven consequential any-sdk PRs.

Closes #705, closes #726, closes #725, closes #710.

Pin bump

• github.com/stackql/any-sdk v0.5.4-alpha01 -> v0.5.5-alpha01 (grpc 1.83.0 -> 1.83.1 follows transitively).
• Closes [BUG] SIGSEGV at plan build for EXEC methods whose response schema lacks an exec parameter property (nil schema admitted into tabulation, typed-nil guard defeated) #705 / Panic (nil pointer) on EXEC with @@json for methods with schema-less response columns #726 on its own: the formulation wrapper no longer wraps a nil schema into a non-nil interface, so the existing col.GetSchema() != nil guard in drm.GenerateSelectDML holds and EXEC against a method whose 2xx schema lacks the exec parameter no longer SIGSEGVs.

Code changes (5 files)

Design notes for review:

• The work order pointed item 1 at unary_selection.go; that path only serves SELECT ... FROM (EXEC ...). Plain SELECT projections are built in astvisit/query_rewriting.go, so both sites call the one helper rather than duplicating the re-keying.
• The select-side descriptor never keys response extraction (that is the insert tabulation, which already carries wire names), so formulation.NewColumnDescriptor with the display name is sufficient; no NewColumnDescriptorWithWireName is needed on this side.
• No new exported types or package-level state. WithDisplayName is a value-receiver method on the existing ColumnHandle struct.
• Optional [BUG] SIGSEGV at plan build for EXEC methods whose response schema lacks an exec parameter property (nil schema admitted into tabulation, typed-nil guard defeated) #705 hardening (attach a default string schema to a param-only projected column) was not taken: the any-sdk fix removes the typed-nil, the drm guard now works, and the robot cases prove it end-to-end.

Test fixtures

Extends the existing no-auth stackql_native_test provider and native_test flask mock (port 1070) rather than adding new ones:

• casing.yaml / mock: IPProtocol query param, storageClass body property, /casing/echo_header (kebab wire header, nativeCasing: kebab), /casing/echo_bodyless/{BinaryId} (body-less EXEC with a metadata-only request block), /casing/activate/{id} (2xx schema {status, requestId} lacking id, the [BUG] SIGSEGV at plan build for EXEC methods whose response schema lacks an exec parameter property (nil schema admitted into tabulation, typed-nil guard defeated) #705 / Panic (nil pointer) on EXEC with @@json for methods with schema-less response columns #726 shape), and an echo_wire resource with no nativeCasing for the SHOW presentation contrast.
• new coerce.yaml service + POST /coerce/echo, PATCH|PUT /coerce/echo/{serviceId} echoing the raw body; settings_body has number, integer, boolean, string properties; insert / update / replace methods with nativeCasing: camel.
• new linked.yaml service + /linked/items, /linked/items_xnext, /linked/items_prev_only: three pages of two, RFC 5988 Link (or X-Next-Page) built from the request host so it works under docker; rows stamp wire_page and the raw query.
• new cursor.yaml service + /cursor/items: base64-padded next_page cursors, 400 on a percent-escaped page=, rows stamp the raw query; resources with and without requestToken.encoding: none.
• odata.yaml / mock: created_at column plus five resources over /odata/people, one per orderBy.syntax (prefix, suffix, column_only, direction_only with supportedColumns: [created_at], explicit odata).
• stackql_oci_testing provider ships the *_envvar defaults pointed at the namespaced STACKQL_OCI_TESTING_* names; the mock now echoes auth_request_target (method + raw request-line URI) so the dangling-? fix is asserted byte-exact.

No entries added to stackql_context.py; every query is inline in its scenario.

Test tooling: registry_rewrite.py now rewrites operation-level servers for patch operations too (previously only get/put/post/delete/head), so the coerce PATCH fixture resolves to the docker host in the Docker Test job instead of localhost inside the container.

One existing expectation updated: Oauth2 CLient Credentials Auth Should Fail with Invalid Config in stackql_mocked_from_cmd_line.robot asserted the request URL with the old dangling ? (.../collectors/100000001?); any-sdk #125 removes it, so the expected error text now reads .../collectors/100000001. That is the only behaviour change surfaced by the existing suites.

Robot scenarios (52 new, all mocked)

Test plan

• go build --tags sqlite_stackql ./... clean on the new pin.
• go test -timeout 1200s --tags "sqlite_stackql" ./... passes.
• golangci-lint run (v2.5.0, CI pin) 0 issues.
• All six touched robot suites pass locally (sqlite backend, native platform): casing 29/29, exec 3/3, body coercion 9/9, rest pagination 11/11, odata pushdown 24/24, oci auth 11/11.
• The other suites on the same provider (function projection, graphql pagination, server variables, xml walker) pass: 38/38.
• Full Stackql Mocked From Cmd Line suite locally: 352/354 after the OAuth2 expectation update; the 2 remaining failures are the known local mTLS key-permission cases (WSL /mnt/c), not regressions.
• CI: build, lint, robot (sqlite + postgres, docker) green.

Not consequential for stackql (no action): any-sdk #134 grpc bump (transitive), #135 CI token fallback.