Use QuickNav Reason

[feerrenrut]

Link to issue number:

Related to PR #12933

Summary of the issue:

When quick nav commands are used, the reason given to speakTextInfo is FOCUS.
This makes it impossible to treat quick nav and focus changed differently.

Description of how this pull request fixes the issue:

OutputReason.QUICKNAV was generally not used, not at all in the chain of calls resulting from speech.speakTextInfo
Treat QUICKNAV in the same way as FOCUS so that they can be differentiated in the future.

Testing strategy:

Merge early in dev cycle, and rely on alpha testing.

Known issues with pull request:

It may be intentional to enforce treating quick nav and focus changed in the same way.

Change log entries:

None

Code Review Checklist:

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