chore(actions): print significat API changes in build summary

[mcollovati]

Prints a summary of the modules whose API changes are computed as 1.0.0 or 0.1.0.

[mcollovati]

Prints a summary similar to the attachment image below, but only if there are modules marked as 1.0.0 or 0.1.0.
The aim is to immediately identify which modules to look at to inspect changes.

[sonarqubecloud]

Quality Gate passed

Issues
0 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 SonarQube Cloud

[github-actions]

Test Results

1 307 files  ± 0  1 307 suites  ±0   1h 15m 46s ⏱️ + 1m 55s
9 270 tests ± 0  9 202 ✅ ± 0  68 💤 ±0  0 ❌ ±0 
9 705 runs   - 21  9 630 ✅  - 20  75 💤  - 1  0 ❌ ±0 

Results for commit 453ef18. ± Comparison against base commit 3d0f854.

[Artur-]

Could/should it print the actual changed methods? Should not matter even if the list is quite long

[mcollovati]

Could/should it print the actual changed methods? Should not matter even if the list is quite long

This would mean reading and parsing the HTML diff file. The idea was simply to show which modules have major changes, so you can open the attached zip file and directly go to the interesting files instead of opening all of them.

[caalador]

This will help a lot with the github api change.