Update birth certificate SVG to use streetLevelDetails fields and correct informant relation handling

[tareq89]

issue: opencrvs/opencrvs-core#10584
core pr: opencrvs/opencrvs-core#10599

Checklist

• I have linked the correct Github issue under "Development"
• I have tested the changes locally, and written appropriate tests
• I have tested beyond the happy path (e.g. edge cases, failure paths)
• I have updated the changelog with this change (if applicable)
• I have updated the GitHub issue status accordingly

[github-actions]

Oops! Looks like you forgot to update the changelog. When updating CHANGELOG.md, please consider the following:

• Changelog is read by country implementors who might not always be familiar with all technical details of OpenCRVS. Keep language high-level, user friendly and avoid technical references to internals.
• Answer "What's new?", "Why was the change made?" and "Why should I care?" for each change.
• If it's a breaking change, include a migration guide answering "What do I need to do to upgrade?".

[Zangetsu101]

Would you be kind enough to figure out why the values aren't consistent? i.e. OTHER, Mother, Father instead of OTHER, MOTHER, FATHER

[Nil20]

@jamil314 has these changes in his PR btw

[tareq89]

@Zangetsu101 , @Nil20 , @jamil314

In v2-events/../pdfUtils.ts, we have the following code:

const resolvedDeclaration = stringifyDeclaration(fieldConfigs, $declaration)

const data = {
  $declaration: resolvedDeclaration,
  $metadata,
  $review: review,
  $references: {
    locations,
    users
  }
}

const output = template(data)
return output

The $declaration object contains all fields with their references resolved into human-readable values.
For example, the field informant.relation is a Select field. Its internal values are uppercase codes like FATHER, MOTHER, while the display labels are Father, Mother, etc.

After resolution, $declaration['informant.relation'] contains the labels (e.g., Father) instead of the raw values (e.g., FATHER).

Hence, when we bind these variables to the template, we use these resolved labels in the final output.

[jamil314]

Does that mean we also need to think about french version of mother/father?

[tareq89]

@jamil314 , I have taken care of your concern in this PR and opencrvs/opencrvs-core#10599 here

[makelicious]

Is the issue only in certified certificate or in all of them?

[makelicious]

Any way to to do this without original declaration? Previously we used native lookup not $lookup, since it provided the raw value. Any guesses what has changed?

[tareq89]

In packages/client/src/v2-events/features/events/actions/print-certificate/pdfUtils.ts

...
  const stringifyDeclaration = getFormDataStringifier(
    intl,
    locations,
    adminLevels
  )
  const fieldConfigs = config.declaration.pages.flatMap((x) => x.fields)
  const resolvedDeclaration = stringifyDeclaration(fieldConfigs, $declaration)
...
  const data = {
    $declaration: resolvedDeclaration,
    $metadata,
    $review: review,
    $references: {
      locations,
      users
    }
  }

As you can see, we first resolve all the properties of the $declaration object, then we send it to svg template. Hence, we dont have any more reference values in $declaration rather always the resolved value.

[tareq89]

We have reverted the change in the core, so now, we dont use resolved value for comparison anymore.