[No QA] Docs updates for E/A#97968 keep currency on personal card CSV re-upload

[MelvinBot]

Explanation of Change

Follow-up docs update for #97968, which fixes re-uploading a CSV to an existing personal card so it preserves the card's original Currency, Card display name, Transactions are reimbursable setting, and Flip amount sign setting (previously it reset to USD and "Imported Card" and created duplicate transactions — see #97887).

The help article Import personal card transactions from a spreadsheet already had an FAQ entry for re-importing to the same card, but it only said "you can simply repeat the import process" and didn't mention that the card's original configuration is retained. This PR updates that FAQ answer to reflect the corrected behavior, using the exact UI labels.

Changed

• docs/articles/new-expensify/connect-credit-cards/Import-Personal-Card-Transactions-From-a-Spreadsheet.md — clarified the "Can I import additional transactions to the same card?" FAQ to explain that a re-upload reuses the card's original currency and settings.

---

@Gonals, 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://16ecd976.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/connect-credit-cards/Import-Personal-Card-Transactions-From-a-Spreadsheet

[MelvinBot]

There's nothing to push here — the only failing check is Check independent approval, and it's not a code failure.

It's failing because the PR has no independent Expensify employee approval yet (approvers: [], independentApprovers: []). That check simply requires a human reviewer other than the author to approve the PR — it can't be resolved by a commit. Every other check (build, validate, verify, spellcheck, etc.) is passing.

So no fix is needed on my end. This will clear once an independent reviewer approves.