Fix RTR bug #3: rewrite morbidity report user comment join via NRT staging CSV

The step "Generating ##SAS_morb_Rpt_User_Comment" joined the Order
observation to itself via root.morb_rpt_uid = obs.observation_uid and
then filtered obs.obs_domain_cd_st_1 IN ('C_Order','C_Result'), which
is impossible because the Order row's obs_domain_cd_st_1 is 'Order'.
The temp table was therefore always empty and MORB_RPT_USER_COMMENT
never populated.

Replaced the broken self-join with a staging-side walk: the upstream
NRT row #nrt_morbidity_observation already carries
followup_observation_uid as a CSV of the Order's children (mixed
C_Order / C_Result / Result), so this step expands that CSV via
CROSS APPLY string_split and joins to #morb_obs_reference filtered to
obs_domain_cd_st_1 = 'C_Result' to pull the user-comment row.

Stays entirely within RDB_MODERN staging — no cross-DB read of
nbs_odse.dbo.act_relationship, consistent with the
sp_nrt_*_postprocessing layer's "NRT-only" convention (cross-DB ODSE
joins live exclusively in sp_*_event SPs).

Verified locally: applied the routine, truncated MORB_RPT_USER_COMMENT,
ran sp_d_morbidity_report_postprocessing for the seeded morb (uid
20080010), confirmed 1 row populated with the seeded user-comment
text. job_flow_log shows step 19 (build ##SAS_morb_Rpt_User_Comment)
and step 27 (Insert into morb_Rpt_User_Comment) both at row_count=1
with no errors.

Author: nullflux

liquibase-service/src/main/resources/db/005-rdb_modern/routines/016-sp_nrt_morbidity_report_postprocessing-001.sql

@@ -799,21 +799,33 @@ BEGIN
 		END;')
 
 
+        -- Find the morb Order's C_Result child (user-comment row) via the
+        -- staging-side projection of the act_relationship graph. The upstream
+        -- NRT row #nrt_morbidity_observation already carries
+        -- followup_observation_uid as a CSV of the Order's children
+        -- (mixed C_Order / C_Result / Result), so this step stays in
+        -- RDB_MODERN staging — no cross-DB read of nbs_odse.dbo.act_relationship.
+        -- The C_Result domain code is what distinguishes the user-comment row
+        -- from lab-result and C_Order siblings.
         SET @sql = N'
         SELECT 	root.morb_Rpt_Key,
                 root.morb_rpt_uid,
-                obs.activity_to_time	 AS user_comments_dt,
-                obs.add_user_id		 AS user_comments_by,
+                cr.activity_to_time	 AS user_comments_dt,
+                cr.add_user_id		 AS user_comments_by,
 				REPLACE(REPLACE(ovt.ovt_value_txt, CHAR(13) + CHAR(10),'' ''), CHAR(10), '' '') AS external_morb_rpt_comments,
                   root.record_status_cd
         INTO '+@SAS_morb_Rpt_User_Comment+'
         FROM '+@tmp_Morbidity_Report+'	as root
-           INNER JOIN #morb_obs_reference AS obs ON root.morb_rpt_uid = obs.observation_uid
-            INNER JOIN #updated_morb_observation_list AS ls ON ls.observation_uid = obs.observation_uid
-            INNER JOIN #tmp_nrt_observation_txt AS ovt ON ovt.observation_uid = obs.observation_uid
+            INNER JOIN #nrt_morbidity_observation AS nmo
+                 ON nmo.observation_uid = root.morb_rpt_uid
+            CROSS APPLY string_split(rtrim(ltrim(nmo.followup_observation_uid)), '','') AS followupObs
+            INNER JOIN #morb_obs_reference AS cr
+                 ON cr.observation_uid    = TRY_CAST(followupObs.value AS bigint)
+                AND cr.obs_domain_cd_st_1 = ''C_Result''
+            INNER JOIN #tmp_nrt_observation_txt AS ovt
+                 ON ovt.observation_uid = cr.observation_uid
         WHERE
-          ovt.ovt_value_txt IS NOT NULL
-          AND obs.obs_domain_cd_st_1 IN (''C_Order'', ''C_Result'');';
+          ovt.ovt_value_txt IS NOT NULL;';
 
         IF @debug = 'true' print @sql;
         EXEC sp_executesql @sql;