[Due for payment 2026-05-12] Conditional useOnyx in ReportActionItemMessage for IOU branch

[cristipaval]

Make useOnyx calls in ReportActionItemMessage conditional so they only fire for IOU-related actions. This is the phase that showed the most consistent metric improvement (-65ms / -8% on ManualSendMessage, -14 subscriptions per message / -27%).

Issue Owner

Current Issue Owner: @mallenexpensify

[cristipaval]

Not overdue

[cristipaval]

Melvin? we have a draft PR. Not overdue.

[LukasMod]

PR ready for review #88691

I found some dead code and was unable to prepare easy QA steps for IOU actions with originalMessage.type of delete, reject, cancel, or approve. I could only get this branch to render locally by mocking report actions in Onyx. I'm not sure if it's truly unused, since we have many more dedicated branches for IOU now and these subtypes may no longer be in use. I decided to keep the rendering as defensive code to avoid a UI regression for edge cases with old user data or BE responses that may still emit these subtypes. It's now guarded by a simple if statement with the logic living there, so the cost is minimal.