P1: replace Any/attribute-discovery customization with typed Protocol registration #57

Tracked by teaql/teaql-conformance#92. Current main@3f289aa exposes many customization entry points as Any and late hasattr/getattr discovery: request policy, checker/fix registry, internal ID, schema provider, app audit sink and runtime telemetry in src/teaql/runtime/context.py. The data-service _SchemaExecutor Protocol also inherits DataServiceExecutor, preventing a truly independent schema contract.

Introduce documented, importable Python Protocols and typed trusted-context registration for the six cuts. Validate capability shape at registration, not after a business request enters the provider. Preserve existing valid callable query policies, generated checker registries and fail-open telemetry adapter behavior. Make schema capability independent of IDataService while keeping context.ensure_schema as the application entry point and bootstrap ordering intact.

Acceptance: positive/denial/failure/lifecycle/provider-not-called tests for each cut, all six replacements composed in one runtime instance, a focused example, exact-main source CI, and a separate immutable internal wheel consumer. Stage this after the P0 Internal ID path; do not infer public release from source or internal gates.