Add-on store: consider 'blocked' when filtering enabled/disabled

[seanbudd]

Link to issue number:

Fixes #15416

Summary of the issue:

When enabling/disabling an incompatible add-on, it is not filtered correctly when toggling filter by enabled/disabled status

Description of user facing changes

Fix bug described in #15416
Add-ons blocked due to compatibility reasons should now be filtered correctly when toggling the filter for enabled/disabled status.

Description of development approach

add additional checks for 'blocked' status when filtering enabled/disabled

Testing strategy:

Manually test disabling and enabling add-ons

Known issues with pull request:

None

Change log entries:

Bug fixes
Add-ons blocked due to compatibility reasons should now be filtered correctly when toggling the filter for enabled/disabled status. (#15416)

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
• Security precautions taken.