Surface format metadata in /api/v1/resolve responses

[kurtseifried]

What

Mirror of CloudSecurityAlliance/SecID-Service issue for format metadata for the self-hosted resolver. Pass through `parsability`, `schema`, `parsing_instructions`, `auth` fields from registry data. Support `?parsability=` filter.

Action items

Same as the SecID-Service issue:

1. Pass through format metadata fields in resolution responses
2. Support `?parsability=structured` query parameter
3. Compose with existing `?content_type=` filter

Spec

See docs/reference/API-RESPONSE-FORMAT.md "Filtering by Parsability" section in the SecID repo.

Dependencies

Use the SecID-Service implementation as the reference (it ships first per the cross-repo work plan).

Acceptance criteria

• Same observable behavior as SecID-Service via this server's REST API
• Python and TypeScript variants both updated
• Tests cover passthrough and filter behavior

🤖 Migrated from CloudSecurityAlliance/SecID's docs/project/TODO.md