Short Answer:
You get to choose when to terminate the application and run the refresh. You DON'T need to quit the application immediately. You have two weeks to plan a convenient time to Quit and Refresh.
Just don't let the 14-day countdown timer reach zero, or the application will terminate, losing all unsaved work.
More explanation:
Snap packages were not originally developed for long-lived desktop applications. They were adapted for that purpose, and sometimes adaptations surprise everybody with unexpected results.
- History: Snap packages, formerly called Click packages, were originally developed for phone applications (which are not always active) a decade ago. Then Snaps became popular with servers and small devices, two segments that don't have desktops. The first experiments with Snaps-on-Desktop were for small, limited-use applications like the desktop calculator.
Snap developers did, in fact, intend this behavior beginning in 22.04 because the alternatives were much worse: Either terminate the application to update (looks like a crash to the user), or don't update at all (security risk). You get to choose when to terminate the application and run the refresh. Just don't let the 14-day countdown timer reach zero, or the application will terminate.
Newer releases of Ubuntu have greatly mitigated this issue. Starting in Ubuntu 23.04, developers added a refresh-upon-close trigger. If you Quit the application and then pause to refresh your beverage momentarily, upon returning and re-launching the application will be refreshed.
- Snap packages MUST refresh. Auto-refresh is a key element of their design. It's one of the most attractive elements to developers, who want to minimize their own support burdens --and user complaints-- by having all users to run a single version of the software regardless of platform. Folks who don't want auto-refresh should not use Snap-packaged software.
Snap handling, like all open-source software, continues to evolve, change, and improve. Developers know about these pain points and are working on them. It can be a slow process --there are a lot of moving parts-- and volunteers to get involved, help, test, and improve the software are welcome.