Track last-updated timestamps per clinical field

New feature: we have a need to capture ‘last updated’ date for: Weight Height Diagnoses 🔎 For investigation: - ❓ Do updatedOn fields already exist for each of these individually? - ❓ What db edits are required for this? new datetime stamp columns for each? Question: all you need to see is when each of these fields were last updated correct? No additional “history” or “past logs” needed? Example: Height: 4’1” (Last updated m/d/y) - yes? KR: correct, we don't need the history. 🛠️ PLAN: Participants' weight, height, and diagnoses change over time as they grow or their condition evolves. Coordinators need to know when each of these values was last recorded — not just when the profile was last touched overall. This adds individual *UpdatedAt timestamps for weight, height, primaryDiagnosis, and secondaryDiagnosis, surfaced in the read-only Clinical Details card via a calendar-clock icon tooltip.

New feature: we have a need to capture ‘last updated’ date for: Weight Height Diagnoses 🔎 For investigation: - ❓ Do updatedOn fields already exist for each of these individually? - ❓ What db edits are required for this? new datetime stamp columns for each? Question: all you need to see is when each of these fields were last updated correct? No additional “history” or “past logs” needed? Example: Height: 4’1” (Last updated m/d/y) - yes? KR: correct, we don't need the history. 🛠️ PLAN: Participants' weight, height, and diagnoses change over time as they grow or their condition evolves. Coordinators need to know when each of these values was last recorded — not just when the profile was last touched overall. This adds individual *UpdatedAt timestamps for weight, height, primaryDiagnosis, and secondaryDiagnosis, surfaced in the read-only Clinical Details card via a calendar-clock icon tooltip.