Link to issue number:

Fixes #15440
Fixup of #15402

Summary of the issue:

Some add-ons have version strings which we cannot parse for ordering.
When checking if an add-on should be force disabled, we don't handle the case where the version string cannot be parsed.
If a version string cannot be parsed, we should assume the add-on should not be force disabled, instead of throwing an error

Description of user facing changes

Add-ons which have unparsable version strings now work again

Description of development approach

If a version string cannot be parsed, we should assume the add-on should not be force disabled, instead of throwing an error

Testing strategy:

Test STR of #15440

Known issues with pull request:

Change log entries:

N/A unreleased regression

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.