Add missing sire and dam dogs that have source data

[asku1990]

Summary

We found that some legacy parent registrations referenced from bearek_id are not present as imported dogs in v2. This causes pedigree completeness percentages to differ from v1 for some virtual pairings.

The fix should be data-driven: add all missing sire and dam dogs to the database when we can find real dog data for them. Do not create placeholder dog rows from registration numbers only.

Concrete example

Virtual pairing:

• Sire: VUOPAJAN WONKALE FI43443/17
• Dam: TAIVALTAJAN DEJAVU FI28258/21
• Depth: 9 generations

v1 shows:

• 9-polven sukutaulusta 81.02 % tiedossa

v2 currently shows:

• 9-polven sukutaulusta tiedossa 80.72 %

The exact gap is 3 known pedigree slots:

• DK08567/79 -> sireRegistrationNo DK14863/77
• DK08567/79 -> damRegistrationNo DK29183/76
• KCSB0114BT -> sireRegistrationNo KCSB0223BF

These parent registrations appear in import issues as missing referenced sire/dam registrations.

Scope

• Review all Referenced sire registration was not found among imported dogs import issues.
• Review all Referenced dam registration was not found among imported dogs import issues.
• For each missing registration, search available trusted source data.
• Add the dog to v2 only when real dog data is available.
• Re-run/import or backfill parent links after adding missing dogs.
• Verify virtual pairing pedigree completeness improves through real data, not placeholders.

Non-goals

• Do not add fake dogs.
• Do not add dog rows with only a registration number.
• Do not change inbreeding math to count unavailable dogs as real dogs.

Acceptance criteria

• Missing sire/dam references with available real dog data are imported or added to the database.
• Parent links resolve for those dogs after backfill/import.
• The example pairing reaches the v1 completeness value when the three missing dogs have real source data.
• Import diagnostics still report only genuinely unresolved parent registrations.