sapi4 32 bit: support voices that don't support pitch or rate (#20432)
### Link to issue number:
<!-- Use Closes/Fixes/Resolves #xxx to link this PR to the issue it is
responding to. -->
Fixes #20302
### Summary of the issue:
Some SAPI4 voices cannot be loaded by NvDA's 32 bit synthDriver host if
they don't support pitch, rate or volume.
### Description of user facing changes:
NvDA no longer fails to load sapi4 voices that do not support pitch,
rate or volume.
### Description of developer facing changes:
### Description of development approach:
* _bridge's synthDriver service: no longer specifically fetch and store
config for pitch, rate and volume when initializing. Rather, do this in
setParam. If the voice is being set, then store all supported params
after the param is set.
### Testing strategy:
* Locally tested a sapi4 voice that did not support pitch.
* [x] Verify issue author can use their particular sapi4 voice.
### Known issues with pull request:
None known.
### Code Review Checklist:
<!--
This checklist is a reminder of things commonly forgotten in a new PR.
Authors, please do a self-review of this pull-request.
Check items to confirm you have thought about the relevance of the item.
Where items are missing (eg unit / system tests), please explain in the
PR.
To check an item `- [ ]` becomes `- [x]`, note spacing.
You can also check the checkboxes after the PR is created.
A detailed explanation of this checklist is available here:
https://github.com/nvaccess/nvda/blob/master/projectDocs/dev/githubPullRequestTemplateExplanationAndExamples.md#code-review-checklist
-->
- [x] Documentation:
- Change log entry
- User Documentation
- Developer / Technical Documentation
- Context sensitive help for GUI changes
- [x] Testing:
- Unit tests
- System (end to end) tests
- Manual testing
- [x] UX of all users considered:
- Speech
- Braille
- Low Vision
- Different web browsers
- Localization in other languages / culture than English
- [x] API is compatible with existing add-ons.
- [x] Security precautions taken.