Dispute notice on order edit page is slow

[shendy-a8c]

Describe the bug

As reported here: p1694347746794979-slack-C03LA109BKM, stores with high number of disputes experience long delay before showing the dispute notice.

I think we need to investigate whether useCharge() call here results in slow database query in server.

Also, if useCharge() can potentially cause slowness, we need to make sure such call in other places does not cause the same problem.

To Reproduce

0. Have high number of disputes.
1. Purchase a product with card 4000000000000259 that will generate dispute right after.
2. Open the order and notice the long delay before the dispute notice shows up.

[zmaglica]

This issue impacts disputes, so assigning to Helix (based on team responsibilities Pc2DNy-3z-p2) @haszari . Assigning as part of Gamma Triage process PcreKM-yM-p2.

[Jinksi]

Moving this to the backlog while we gather more information about the problem via the tracks event introduced in #7437 – will help us determine if we still need to improve the performance or change how we deliver the message.

[haszari]

This is not a high priority issue. Before taking action here we need to be clear (and aligned) on what stores are affected, and how much they are affected.

• How many disputes are needed to trigger the slowness?
  • Sub-question: how many of our merchant have this many disputes? I.e. what % of merchants are affected.
• What's the performance penalty on displaying the notice (i.e. time to display for 1-10 disputes vs. for many)?

Downgrading to medium, though this may be low priority once we understand the impact.

[Jinksi]

What's the performance penalty on displaying the notice (i.e. time to display for 1-10 disputes vs. for many)?

FYI for whoever explores this: some measurements of performance for a high-dispute-count-store (WCCOM) were included in PR #7174.