Fixed SAPI5 initialisation (#17513)
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.
