feat: Fire an event when all hotswap operations have completed

[Artur-]

No description provided.

[github-actions]

Test Results

1 142 files  +26  1 142 suites  +26   1h 23m 51s ⏱️ - 3m 11s
7 474 tests +26  7 424 ✅ +26  50 💤 ±0  0 ❌ ±0 
7 847 runs  +56  7 787 ✅ +56  60 💤 ±0  0 ❌ ±0 

Results for commit dea30c2. ± Comparison against base commit f1c9673.

♻️ This comment has been updated with latest results.

[mcollovati]

Looks good.
Does it make sense to have a generic HotswapEvent (and maybe an HotswapSessionEvent) and refactor VaadinHotswapper adding methods to have it as a parameter, deprecating the existing ones? (default implementation would call the existing ones until they will be removed)

[Artur-]

The main reason to have an event is to be able to extend or modify it without breaking existing code. A common super class does not seem super important but maybe good design if you introduce event classes for the other methods, which also could be a good idea. For a separate PR :)

[sonarqubecloud]

Quality Gate passed

Issues
86 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[vaadin-bot]

This ticket/PR has been released with Vaadin 24.6.0.alpha2 and is also targeting the upcoming stable 24.6.0 version.