Docs updates for E/A#96364 broken card connection 90-day grace period

[MelvinBot]

Explanation of Change

Documentation follow-up for #96364 (fix for #91451), which changes how broken card-connection indicators behave once a card/feed has gone 90 days or more without a successful sync.

That PR intentionally keeps the error on the card/feed so it stays fixable, but suppresses the proactive reminders past the grace period:

• Personal cards: the Time Sensitive notification on Home and the red dot on Wallet in the navigation tabs stop showing. The card still appears in Wallet with its red dot and can be fixed via Fix card.
• Company cards: the Time Sensitive notification on Home and the red dot on the workspace row stop showing. For direct (bank-connected) feeds, the “Card feed connection is broken” banner remains on the Company cards page so a Workspace Admin can still reconnect.

The existing help articles list those indicators as the way to detect a broken connection, but don't mention that they stop appearing after ~90 days. Without this note, a user (or admin) with a long-broken connection would look for reminders that are no longer there. This PR adds a short clarifying note plus an FAQ entry to each affected article.

Files changed

• docs/articles/new-expensify/connect-credit-cards/Manage-Personal-Cards.md — clarifying note under the indicator list + new FAQ entry.
• docs/articles/new-expensify/connect-credit-cards/Fix-a-Broken-Company-Card-Feed-Connection.md — clarifying note under the indicator list + new FAQ entry.

Changes are additive only — no existing labels, headings, or steps were altered. All UI labels reused verbatim from the existing articles (Time Sensitive, Home, Wallet, Company cards, Fix card, “Card feed connection is broken”). The Account > Wallet navigation labels were verified against the live web UI; the broken-connection-specific labels weren't reachable in the test account (no cards/workspaces present), so they were kept identical to the already-published articles.

---

@wildan-m, 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.