fix: symtab registers snake display column names + robot coverage for AWS e2e casing/walker behaviours (any-sdk v0.5.3-alpha11) - #679

Description

Companion to stackql/any-sdk#114, shaken out by live end-to-end lifecycle testing (INSERT / SELECT / UPDATE / DELETE) of the new native AWS provider across all four wire protocols (ec2, query, aws-json, rest-xml).

Core fix:

• statement_analyzer: the symbol table now registers the tabulated display column names alongside the raw property keys. Under config.snake_case_aliases, a WHERE clause can reference the snake alias of a response column (previously SELECT ... WHERE vpc_id = ... failed with could not locate symbol vpc_id whenever vpc_id was a response column rather than a request parameter). Without aliasing, the tabulation re-registers the same names - a no-op.

Bump: any-sdk v0.5.3-alpha10 -> v0.5.3-alpha11, consuming the casing-surface parity and schema-driven XML walker fixes from stackql/any-sdk#114.

Robot coverage (new fixture resources in the stackql_native_test provider + flask mock endpoints):

• stackql_casing.robot (4 new cases): DESCRIBE EXTENDED renders snake aliases; SELECT * projects values through snake-aliased star expansion (previously wire-cased identifiers resolved as string literals on a case-sensitive backend, so every value projected as its own column name); a snake WHERE key satisfies a REQUIRED PascalCase wire parameter during method routing and reaches the wire re-keyed; request.base: '{}' fallback body is sent verbatim when no body fields exist (the aws-json no-input pattern).
• stackql_xml_walker.robot (5 new cases): member-name schema properties with xml: name overrides project values (the AWS provider Display shape); nested wire elements JSON-stringify under string-typed columns; a snake response-column WHERE post-filters via the symtab fix; CreateVpc-style singleton unwrap projects (what makes INSERT ... RETURNING work); an empty 200 body yields zero rows.

Type of change

• Bug fix (non-breaking change to fix a bug).
• Feature (non-breaking change to add functionality).
• Breaking change.
• Other (eg: documentation change). Please explain.

Issues referenced.

• fix: casing-surface parity + schema-driven XML walker gaps from AWS p… any-sdk#114 (fixes consumed via the v0.5.3-alpha11 bump)
• Follows consume any-sdk v0.5.3-alpha08 (casing + schema_driven_xml) + robot coverage #678

Evidence

All verified locally (Linux/WSL, sqlite backend):

• Robot functional: stackql_casing + stackql_xml_walker suites - 22/22 pass (13 pre-existing + 9 new cases).
• Unit: go test -timeout 1200s --tags "sqlite_stackql" ./... - pass.
• Live end-to-end against real AWS with the provider under development: 20/20 offline DESCRIBE checks, 20/20 live SELECT shape checks, and full DML lifecycles on all four protocols - aws.ec2.vpcs (7 steps: INSERT+RETURNING, list, get, UPDATE via nested-struct attribute, verify, DELETE with snake key, confirm gone), aws.sns.topics (6 steps), aws.dynamodb.tables (6 steps incl. list-of-struct CreateTable body), aws.s3.buckets (4 steps) - 43/43, every created resource torn down by DELETE and its absence verified.

Checklist:

• A full round of testing has been completed, and there are no test failures as a result of these changes.
• The changes are covered with functional and/or integration robot testing.
• The changes work on all supported platforms.
• Unit tests pass locally, as per the developer guide.
• Robot tests pass locally, as per the developer guide.
• Linter passes locally, as per the developer guide.

Variations

• Platform coverage: verified locally on Linux (WSL) only; relying on CI matrix builds (Windows / macOS / macOS ARM) for the remaining platforms - the change surface is platform-independent Go and test assets.
• Linter: not run locally; relying on the CI lint gate. The non-test source delta is one bounded block in statement_analyzer.go.

Tech Debt

None accrued. The symtab change registers aliases through the existing tabulation path (no new naming scheme), and the robot fixtures reuse the established stackql_native_test provider + flask mock pattern. One upstream behavioural note is documented in any-sdk #114 rather than here: request.default diverts supplied body params in the armoury flow, so the aws-json empty-body pattern uses request.base.