#22086: fix(tts): honor explicit config provider and model/voice settings

## Summary - Preserve explicit `messages.tts.provider` precedence over persisted runtime preferences in `getTtsProvider`. - Keep existing behavior where runtime prefs are used only when no provider is explicitly configured in config. - Add regression coverage for: - config provider overriding persisted `/tts` provider preference - OpenAI TTS request body using configured `model` and `voice` ## Why Issue [#22005](https://github.com/openclaw/openclaw/issues/22005) reports explicit `messages.tts.openai.*` settings being ignored. A persisted TTS provider preference can out-prioritize explicit config, so explicit OpenAI config values were effectively bypassed. ## Validation - `pnpm exec oxlint --type-aware src/tts/tts.ts src/tts/tts.test.ts` - `pnpm exec oxfmt --check src/tts/tts.ts src/tts/tts.test.ts` - `pnpm vitest run --config vitest.unit.config.ts src/tts/tts.test.ts` Closes #22005 <!-- greptile_comment --> <h3>Greptile Summary</h3> Fixed TTS config provider precedence to ensure explicit config settings override persisted runtime preferences. Also preserved approved device scopes across token rotations and kept UI chat draft text during abort operations. Key changes: - Reordered `getTtsProvider` logic to check `config.providerSource === "config"` before checking persisted `prefs.tts?.provider` - Added `approvedScopes` field to `PairedDevice` type to track all scopes ever approved for a device - Updated device pairing and token rotation to accumulate scopes into `approvedScopes` via `mergeScopes` - Modified gateway message handler to use `approvedScopes` (if present) when validating reconnection attempts - Removed `host.chatMessage = ""` from `handleAbortChat` to preserve typed draft text - Added comprehensive test coverage for all three fixes <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with minimal risk - The changes are well-isolated, properly tested with comprehensive coverage (37 passing tests), and address specific bugs without introducing breaking changes. The TTS fix correctly reorders precedence checks, the device pairing changes safely add a new optional field while maintaining backward compatibility, and the UI change is a simple one-line removal that preserves expected behavior. - No files require special attention _{Last reviewed commit: be2a0e5} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->