fix(kyc): declare financial question conditions in the API contract

[joshuakrueger-dfx]

Why

GET /kyc/data/financial/:id returns the questionnaire. Each question can carry conditions, which
say under what earlier answer the question applies at all — FinancialService.getQuestions has
mapped the field through since #2071 (2025-04):

conditions: q.conditions,

KycFinancialQuestion never declared it. The field is therefore invisible in the Swagger contract
and absent from generated clients, so a consumer cannot reproduce which questions are still
outstanding for a given set of answers — it has to submit and find out from the result. That is the
wrong way round: the same completeness logic the backend runs in FinancialService.isComplete
depends entirely on conditions.

What changed

• KycFinancialCondition (question, response) added, matching the shape in
  financial-questions.ts.
• conditions?: KycFinancialCondition[] declared on KycFinancialQuestion as
  @ApiPropertyOptional with isArray, so questions without preconditions keep omitting it.

No runtime change. This PR only writes down what the endpoint already sends.

Tests

One new spec, checked in both directions against the production mapping it pins:

Probe	Result
conditions: q.conditions removed from getQuestions	1 of 1 fails
Mutation conditions: q.conditions → conditions: []	1 of 1 fails

financial.service.ts was restored after each probe and verified clean (git diff empty), so the
probes did not leave the mapping altered.

Full gate on the exact revision 1cbf51e5e: lint (empty output), format:check, type-check
and build all exit 0; Test Suites: 340 passed, 340 of 347 total,
Tests: 6206 passed, 174 skipped, 6380 total; coverage gate exit 0.

The spec derives its expectations from getFinancialQuestions instead of naming questions, so it
breaks when the mapping breaks, not when a question is renamed. It asserts up front that the catalog
contains both questions with and without conditions, so it cannot pass vacuously if that ever stops
being true.

Scope

Only kyc-financial-out.dto.ts and its spec. financial.service.ts is untouched — the mapping was
already correct.