Normalize iouComment to markdown before rendering

The description field of a saved transaction is stored as HTML
(e.g. <a href="https://google.com">google.com</a>), but
MoneyRequestConfirmationListFooter feeds it into a MenuItemWithTopDescription
with shouldParseTitle, which runs ExpensiMark markdown-to-HTML on the value.
When the input is already HTML, ExpensiMark HTML-escapes the <a> tags, so
the user sees raw <a href=...>google.com</a> text on the Split details page.

Prior to the 'remove redundant props' refactor, SplitBillDetailsPage
normalized the stored HTML with Parser.htmlToMarkdown() before passing
iouComment down. That normalization was dropped when iouComment moved to
a single internal derivation in MoneyRequestConfirmationList. Restoring
the htmlToMarkdown call at the producer keeps every downstream consumer
(shouldParseTitle menu item and type='markdown' text input) consistent
for both draft (plain text) and saved (HTML) transactions, and avoids
regressing auto-linking of bare URLs in draft confirmation flows.

Author: wildan-m

src/components/MoneyRequestConfirmationList.tsx

@@ -26,6 +26,7 @@ import Log from '@libs/Log';
 import {validateAmount} from '@libs/MoneyRequestUtils';
 import Navigation from '@libs/Navigation/Navigation';
 import {getIOUConfirmationOptionsFromPayeePersonalDetail, hasEnabledOptions} from '@libs/OptionsListUtils';
+import Parser from '@libs/Parser';
 import {getTagLists, isAttendeeTrackingEnabled, isTaxTrackingEnabled} from '@libs/PolicyUtils';
 import {isSelectedManagerMcTest} from '@libs/ReportUtils';
 import type {OptionData} from '@libs/ReportUtils';
@@ -291,7 +292,11 @@ function MoneyRequestConfirmationList({
     const isGPSDistanceRequest = isGPSDistanceRequestUtil(transaction);
 
     const iouAmount = hasValidModifiedAmount(transaction) ? Number(transaction?.modifiedAmount) : (transaction?.amount ?? 0);
-    const iouComment = getDescription(transaction);
+    // `getDescription` returns the raw `transaction.comment.comment`, which is stored as HTML for saved
+    // transactions (e.g. viewing a completed split on `SplitBillDetailsPage`). Normalize to markdown here
+    // so every downstream consumer (`shouldParseTitle` menu item and `type="markdown"` input) receives
+    // a consistent format regardless of whether the transaction is a draft (plain text) or a saved one (HTML).
+    const iouComment = Parser.htmlToMarkdown(getDescription(transaction));
     const iouCurrencyCode = getCurrency(transaction);
     const iouMerchant = getMerchant(transaction);
     const iouCreated = getCreated(transaction);