ci: dispatch validation after automated pushes

[daggerok]

Root cause

GitHub does not create a push workflow run for commits pushed with GITHUB_TOKEN. The dependency-update workflow pushed its dependency commit with that token, so CI did not run; only the explicitly dispatched GitHub Pages workflow ran.

Fix

• explicitly dispatch ci.yaml after a successful automated dependency push
• explicitly dispatch ci.yaml after a successful SEC-data refresh push
• guard both dispatches with a pushed step output, so no CI run is requested when there is nothing to commit or a push fails
• grant the data-refresh workflow actions: write permission required for workflow dispatch
• remove [skip ci] from the data-refresh commit message

Normal user pushes remain covered by CI's existing on: push trigger. These explicit dispatches cover the GitHub-token automation exception.

Action release refresh

This PR also applies the current stable action major tags across all workflows: checkout v7, cache v6, configure-pages v6, upload-pages-artifact v5, deploy-pages v5, setup-uv v8; setup-bun v2 was already current.

Validation

• YAML syntax validated for all workflow files

No master changes were made directly.