Fix the link for "Build (for testing PR)" in appVeyor message

[CyrilleB79]

Link to issue number:

Probably fix-up of #17214.
Follow-up of #17249.

Summary of the issue:

When an appVeyor test failure message is issued, the build link in this message is on l10nUtil.exe rather than on nvda_snapshot_xxxx.exe.

Description of user facing changes

The NVDA snapshot executable will be again downloadable from appVeyor messages.

Description of development approach

Refine the filtering to find the snapshot executable on "nvda_.exe" rather than on ".exe", as done in the deploy script in #17249 in appVeyor script.

Testing strategy:

Introduce an error in unit tests to trigger the message and check the result: see #17510 (comment).

Known issues with pull request:

None

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.

@coderabbitai summary

[AppVeyorBot]

• PASS: Translation comments check.
• PASS: License check.
• FAIL: Unit tests. See test results for more information.
• PASS: Lint check.
• PASS: System tests (tags: installer NVDA).
• Build (for testing PR): https://ci.appveyor.com/api/buildjobs/66j3b9f1ijp7nu8k/artifacts/output/nvda_snapshot_pr17510-34767,34e60e70.exe
• CI timing (mins):
  INIT 0.0,
  INSTALL_START 1.2,
  INSTALL_END 1.0,
  BUILD_START 0.0,
  BUILD_END 26.4,
  TESTSETUP_START 0.0,
  TESTSETUP_END 0.4,
  TEST_START 0.0,
  TEST_END 19.0,
  FINISH_END 0.2

See test results for failed build of commit 34e60e7017

[seanbudd]

Thanks @CyrilleB79