Fix SAPI 5 initialisation

[SaschaCowley]

Link to issue number:

Closes #17512
Fix-up of #17496

Summary of the issue:

After the removal of winmm support, SAPI5 synthesisers failed to initialise.
This is because we switched from integer-based IDs as used by winmm, to ID strings as used by Windows Core Audio.

Description of user facing changes

SAPI5 synthesisers now initialise correctly.

Description of development approach

Rather than calling outputDeviceNameToID to index into the audio outputs returned by SAPI, iterate over them and look for one whose Description matches the friendly name of the output device to use as stored in the user's config.

Testing strategy:

Tested loading SAPI5 with a number of output devices selected, and changing output devices with SAPI5 loaded.

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.
• PASS: Unit tests.
• PASS: Lint check.
• FAIL: System tests (tags: installer NVDA). See test results for more information.
• Build (for testing PR): https://ci.appveyor.com/api/buildjobs/eh00d9amc1dccuky/artifacts/output/nvda_snapshot_pr17513-34791,1c6a4fbd.exe
• CI timing (mins):
  INIT 0.0,
  INSTALL_START 1.2,
  INSTALL_END 0.9,
  BUILD_START 0.0,
  BUILD_END 27.3,
  TESTSETUP_START 0.0,
  TESTSETUP_END 0.4,
  TEST_START 0.0,
  TEST_END 19.0,
  FINISH_END 0.1

See test results for failed build of commit 1c6a4fbd0c

[burmancomp]

Works for me. This should be merged as soon as possible.