show all channels for updatable add-ons if a beta/dev add-on has been installed

[seanbudd]

Link to issue number:

None

Summary of the issue:

If a beta/dev add-on has been installed, updates for that add-on are not displayed by default when going to the updatable add-ons tab.
This is because the default channel view for updatable add-ons is always "Stable".
Instead, it would be helpful to show beta/dev add-ons if these have been installed previously.

Description of user facing changes

If a beta/dev add-on has been installed, add-ons of all channels will show up by default in the updatable add-ons tab

Description of development approach

Set the filter key depending on if beta/dev add-ons have been installed

Testing strategy:

Manual testing by installing a beta add-on

Known issues with pull request:

Note: this switches the default to all if any beta/dev add-on has been installed, not necessarily the one with updates available

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.

[AppVeyorBot]

• PASS: Translation comments check.
• PASS: Unit tests.
• FAIL: Lint check. See test results for more information.
• PASS: System tests (tags: installer NVDA).
• Build (for testing PR): https://ci.appveyor.com/api/buildjobs/gac1ovgyms2qk4gi/artifacts/output/nvda_snapshot_pr16637-32202,c8931fc3.exe
• CI timing (mins):
  INIT 0.0,
  INSTALL_START 1.0,
  INSTALL_END 0.9,
  BUILD_START 0.0,
  BUILD_END 11.5,
  TESTSETUP_START 0.0,
  TESTSETUP_END 0.4,
  TEST_START 0.0,
  TEST_END 2.3,
  FINISH_END 0.2

See test results for failed build of commit c8931fc3e8

[CyrilleB79]

@seanbudd, this strategy cause the following issue:

If I collaborate on an add-on, e.g. Windows Essential, I want to follow dev channel. For all my other installed add-ons (e.g. Instant Translate, Outlook Extended), I want to stick on the stable channel. When updates are available, I'd like to display dev channel for Windows Essential but only stable for Outlook Extended or Instant Translate, so that I can select all in updatable add-on tab and update.

The solution, although technically more complex, would be to have a filter displaying stable updates for stable add-ons, beta updates for beta add-ons and dev updates for dev add-ons.

[seanbudd]

@CyrilleB79 - I see this as a separate use case outside of the scope of this PR. I think this could be implemented by creating a new channel filter key for "same channel" in the updatable tab

[seanbudd]

See also #16636 which may cover your use case as auto-updates and update notifications will only be for the same channel in the first implementation