fix: trigger SonarCloud after release and remove redundant main push …

[luluiz]

User-Facing Changes

N/A

Description

After a release, the SonarCloud analysis on main was showing an outdated project version and stale code coverage because:

1. The release.yml commit uses [skip actions], which skips all workflows — including SonarCloud
2. The previous push-triggered Sonar analysis ran on the merge commit (before the version bump), so it always reported the old version

This PR fixes the issue by:

• Adding a step in release.yml to explicitly trigger the SonarCloud workflow on main via gh workflow run after the release is complete — ensuring analysis runs with the correct version
• Removing main from the push trigger in sonarqube.yml to avoid a redundant (and outdated) Sonar run on every merge to main

Related to #1009

Checklist

• The web version was tested and it is running ok
• The desktop version was tested and it is running ok
• This change is covered by unit tests
• Files constants.ts, types.ts and *.style.ts have been checked and relevant code snippets have been relocated

[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