Add-on Store update notifications should provide a ding on appearing, and should appear immediately on NVDA startup

[XLTechie]

Is your feature request related to a problem? Please describe.

The updatable add-ons window, doesn't appear the first time until a couple minutes after NVDA starts. That gives you just enough time to start doing something, and then have the window appear and interrupt you.

At first I didn't think this was much of a problem. After all, Add-on Updater has done the same thing for years.
But after considering it, I realize that Add-on Updater's window, appears immediately upon NVDA start. You don't have time to get into something else, and then have the updates window appear and disrupt your workflow. Therefore, it doesn't come off as nearly so obtrusive.

That aside, there is another issue. The Available Updates window appears, takes focus, and doesn't make it obvious that whatever you were doing, you aren't doing any more. So for a few seconds at least, if you were rapidly typing or the like, you'll still be doing that, but into the updates window.

Describe the solution you'd like

1. Run the initial updates check, as soon as NVDA starts--as soon as practical, not after a two minute delay.
2. Play a sound, or at least use the Windows alert sound, to signal the user that some kind of notification or window has appeared. It will not be perfect, but it is better than silently steeling focus. This is mostly to be useful when NVDA has been running for 24 hours, and the Available Updates window is appearing again, not after first appearing when starting NVDA.

Describe alternatives you've considered

Additional context

This is essentially the same issue as #17037, filed by @cyrmax. However the proposed solutions here are different, and irrespective of whether a toast notification mechanism is eventually implemented.

[RuturajL]

I propose following as a potential solution:
NVDA should use built-in Windows Notifications UI for delivering availability of addons.
The notification should be actionable, where clicking on that notification, or an update button in that notification, the addons update window opens, where the user can do further actions. If they don't want to take action, Notification simply stays in notification area for later use.
This could be also utilized for NVDA update notifications as well.
Potential things we might need to consider is backwards compatibility, Do Win10 and 11 use the similar APIs to deliver notifications?

[CyrilleB79]

If I remember correctly, the update dialog does not pop up at startup to avoid that all dialogs pop up at the same time (welcome, stats, NVDA update, add-on update).

Rather than using the current schedule approach to guarantee that all dialogs do not pop up together, could we schedule one dialog immediately the previous one has been validated? e.g. open welcome dialog (if needed), when it's closed, open stat dialog, when it's closed, open add-ons update dialog (if applicable), and when it's closed, open NVDA update dialog (if applicable).

This way, one dialog would pop up just after another is closed (or just after the connection to retrieve update information), avoiding to interrupt a task