Reword stale removed-from-QBO vendor comment to reference the accounting integration generically

[MelvinBot]

Explanation of Change

This is a comment-only change — no runtime behavior is affected.

The inactiveVendor violation was recently generalized in Auth (Auth#23497) so it now fires for Sage Intacct and Xero in addition to QuickBooks Online. A stale inline comment in IOURequestStepVendor.tsx still described the cleared vendor as "removed-from-QBO", which is now inaccurate. This reworks it to reference the accounting integration generically ("removed from the accounting integration").

This is follow-up 2 from Expensify/Expensify#668349.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/668349
PROPOSAL:

Tests

Comment-only change; no functional behavior changes. Nothing to test at runtime.

• Verify that no errors appear in the JS console

Offline tests

N/A — comment-only change.

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[MelvinBot]

The only failing checks are non-code checks that I can't resolve by pushing to the branch — every actual code/test check is green.

Failing:

• checklist — "PR Author Checklist is not completely filled out (0 of 38 items)." This just needs the boxes in the PR Author Checklist section to be checked off by a human. Since this is a comment-only change, the QA section still has the // TODO placeholder — either fill in the checklist + QA steps or add [No QA] to satisfy it.
• Check independent approval — needs an independent reviewer's approval; not something code changes can clear.

Passing: Bun tests, ESLint, Oxfmt, typecheck, Storybook, React Compiler, spellcheck, and all 8 Jest test jobs. The remaining build (...) and *-perf-tests checks are still pending, not failed.

There's nothing for me to fix in the code — this PR just needs the author checklist completed and a reviewer approval.

[MelvinBot]

Still the same two non-code checks failing — nothing I can push a fix for:

• checklist — the PR Author Checklist is unchecked (0/38). A human needs to check the boxes, and since this is a comment-only change, either complete the checklist + QA steps or add [No QA] to the title.
• Check independent approval — needs an independent reviewer's approval.

Every code/test check (Bun tests, ESLint, Oxfmt, typecheck, Storybook, React Compiler, spellcheck, all 8 Jest test jobs) is green. The build (...) and *-perf-tests checks are still pending, not failed. There's no code change for me to make here.