[No QA] Docs updates for E/A#98622 document bank connection re-authentication error

[MelvinBot]

Explanation of Change

Companion help-site update for #98622, which distinguishes bank re-authentication scrape codes (438/532) from a generic broken bank connection and gives users a clearer in-app message: "Bank connection needs re-authentication" instead of the generic "broken bank connection" copy.

The resolution path (a Workspace Admin reconnects the card feed from Company cards) is unchanged and already documented, but the existing article had no troubleshooting entry for the re-authentication scenario. This PR adds that.

Updated docs/articles/new-expensify/connect-credit-cards/Fix-a-Broken-Company-Card-Feed-Connection.md:

• Added a bullet noting that an expense/receipt can surface a pending message when the connection is broken or needs re-authentication.
• Added a troubleshooting entry, Error: Bank connection needs re-authentication, explaining what it means and how to reconnect.

Scope notes

• The App PR only refines in-app violation microcopy; it adds no new feature or flow. The re-authentication copy is dormant until the coupled Auth change deploys.
• UI labels used (Company cards, Home, Time Sensitive) match the terminology already present in this verified article; exact new copy was taken from the App PR diff.

Related

• [Payment due @situchan] Distinguish re-authentication scrape codes (438/532) in RTER violation copy #98622

---

@tgolen, please review the files changed and confirm they reflect the current behavior. Then post a new comment saying @MelvinBot mark this PR as ready for review.

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://a35d691f.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/connect-credit-cards/Fix-a-Broken-Company-Card-Feed-Connection