fix: accept exact loader bar schemas for feature inputs

[pjy008008]

Summary

• accept the operating loader's explicit market-bars/1 base and derived Parquet schemas as feature inputs
• bind legacy acceptance to exact producer metadata (Alpaca SIP/raw, resolution, manifest ID)
• keep unknown versions, schema drift, and metadata drift fail-closed

Operational evidence

The development catalog has 96 AVAILABLE loader manifests and 768 receipts using market-bars/1. Live samples confirmed 30m uses the base schema while 1h/4h/1d use the derived schema with source_bar_count and source_minutes.

Validation

• red test first: both exact legacy schemas were rejected before the change
• 109 passed, 2 deselected across feature backfill/output trust-boundary tests
• ruff check passed
• mypy apps/pipeline_worker/feature_output.py passed

The deselected tests are Docker-backed integration tests; the local root backend pointer currently lags the vendored central-migration fixture (§2.7), which is unrelated to this patch.