Allow config profile triggers when Add-on Store is open (#19583)
Closes #15165
Summary of the issue:
Configuration profile triggers for "Current application" do not activate when the Add-on Store dialog is open, even though the Add-on Store is an NVDA window. This is because AddonStoreDialog inherits from SettingsDialog, which has shouldSuspendConfigProfileTriggers = True to prevent feedback loops while editing settings.
Description of user facing changes:
Configuration profile triggers now activate when the Add-on Store is open. Users who create a config profile triggered by the NVDA application (e.g., to enable table headers in the Add-on Store) will now have their profile correctly activated.
Description of developer facing changes:
Added shouldSuspendConfigProfileTriggers = False to AddonStoreDialog to override the inherited value from SettingsDialog.
Description of development approach:
The SettingsDialog base class sets shouldSuspendConfigProfileTriggers = True because changing settings while a profile trigger is active could cause confusion. However, the Add-on Store doesn't modify NVDA settings, so there's no reason to suspend triggers. The fix simply overrides this attribute to False.
