ci: run workflows on renovate/** branches

[setchy]

What

Add the renovate/** branch pattern to the push triggers so CI runs on Renovate's update branches before they are pushed/merged.

Files: .github/workflows/lint.yml, .github/workflows/test.yml, .github/workflows/sonarcloud.yml, .github/workflows/zizmor.yml

Why

Renovate is switching gitify-app/renovate-config workflow digest updates to branch automerge (automergeType: "branch", see gitify-app/renovate-config#9). That mode creates a branch and, once it's up to date and green, pushes the commit straight to the base branch — no PR.

Renovate waits for the branch's status checks. Our workflows currently trigger only on push: main + pull_request, so a renovate/** branch runs no checks and Renovate would eventually fall back to opening a PR (~25h). Renovate's docs explicitly require adding renovate/** to the testing workflow triggers for branch automerge.

Impact

• CI now also runs on renovate/** branches (every Renovate update branch in this repo, not just the digest bump).
• No change to main or PR behavior.

Follow-ups (outside this repo)

• Renovate must be a bypass actor with mode "Always allow" on the default-branch ruleset so it can push directly to the protected main; otherwise the push is rejected and it falls back to a PR.

[netlify]

✅ Deploy Preview for gitify ready!

Name	Link
🔨 Latest commit	f103aa1
🔍 Latest deploy log	https://app.netlify.com/projects/gitify/deploys/6acfa99e0d3c2de6c2bb2d41
😎 Deploy Preview	https://deploy-preview-788--gitify.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 93 Accessibility: 100 Best Practices: 100 SEO: 100 PWA: - View the detailed breakdown and full score reports
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[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

[setchy]

Closing — no longer needed. We're keeping PR-based automerge for the gitify-app/renovate-config digest updates, so CI continues to run via the existing pull_request trigger. The renovate/** push trigger is only required for branch automerge, which we're not adopting.