Add-on store: bypass the compatibility checks for an add-on (#14797)
Part of #13985
Summary of the issue:
A user may wish to over-ride compatibility issues with an add-on at their own risk.
This should only be possible when an add-on is incompatible due to API breaking changes, i.e when the last tested version of NVDA is not recent enough.
Compatibility overrides should be reset when:
updating to an API breaking version of NVDA
updating an add-on
disabling an add-on
removing an add-on
Description of user facing changes
Users are warned rather than blocked when attempting to enable or install an incompatible add-on.
Warning has been updated when updating to an API breaking version of NVDA.
Incidentally to this PR:
adds several actions to the add-on store: enable, disable, remove, add-on help
focus is moved to the add-on status after performing an action on an add-on
Description of development approach
Added a state tracker in addonHandler to track add-ons which have been disabled for compatibility reasons.