[No QA] Docs updates for E/A#97333 AUS Corpay certification TMD, illion report, bank statement

[MelvinBot]

Docs updates for E/A#97333

This draft updates the NewDot Global Reimbursement - Australia help article to reflect the AUS Corpay certification changes introduced in #97333.

What changed in the PR

The PR updated the AUD (Australia) non-USD bank account / Corpay setup flow with three user-facing changes:

1. TMD added to the disclosure paperwork — the disclosure documents shown during setup now include Corpay's Target Market Determination (TMD) alongside the existing Financial Services Guide (FSG) and Product Disclosure Statement (PDS).
2. illion report requirement for signers — both signers must be listed as directors on the company's illion report; they can't be any two people at the business.
3. Bank statement upload — a recent bank statement, dated within the last three months, is now requested for the business bank account being connected.

Help site changes made

Updated docs/articles/new-expensify/wallet-and-payments/Global-Reimbursement-Australia.md:

• Added the illion report signer requirement and the recent-bank-statement requirement to Australia Document Requirements.
• Added a note under Add Director Information that both signers must be listed as directors on the company's illion report.
• Added a new Review the Disclosure Paperwork and Provide a Bank Statement step documenting the FSG, PDS, and TMD disclosure documents plus the recent bank statement, and renumbered the subsequent steps.

@madmax330, 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://bf3d560a.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/wallet-and-payments/Global-Reimbursement-Australia

[MelvinBot]

I checked the CI on this PR. Every code/content check is passing (build, check, verify, validate, dryRun, spellcheck, CLA, verifySignedCommits). There's nothing to fix by pushing.

The only red check is Check independent approval, which isn't a code failure — it's a gating check that stays red until an independent reviewer approves the PR. It can't be resolved with a commit; it clears once this docs update gets a review/approval.

Next step: review the changed help article and, if it looks good, approve the PR (or reply @MelvinBot mark this PR as ready for review per the description). That will satisfy the approval gate.