Move the checks onto the shared umbrella and build the other dev branch weekly [ignore_release]

[snake14]

Description

Three separate changes, one per commit so any can be reverted on its own.

The pull request checks move behind the shared umbrella. The workflows this replaces were already thin callers of the same shared workflows, so what changes is that one caller invokes them rather than several. The point is that a check added centrally now reaches this plugin without a pull request here. It also drops the concurrency group the AI checklist workflow carried — that group spans both of the umbrella's lanes and silently defeats them, which the shared workflow now fails the run on.

The non-default dev branch gets a weekly build. GitHub only runs a schedule trigger from the default branch's copy of a workflow file, so when the default moved the other line stopped being built and nothing said so. The sweep dispatches this plugin's own matomo-tests.yml on that branch using this repository's own token — workflow_dispatch is a documented exception to the rule that GITHUB_TOKEN-triggered events create no workflow run, so no PAT is involved. The cron keeps this plugin's own minute and hour, moved to Sunday, so it does not compete with the Saturday build and the fleet keeps its stagger.

The pre-push hook is re-synced to the canonical copy, and verify-hook: true turns on the check that keeps it there. The local copy had drifted well behind — it predates the fix for PHPStan exiting 1 when a plugin's config excludes every changed file, so a test-only push was rejected. The flag and the re-sync are in one commit deliberately: enabling the check against a drifted copy would just go red.

Verified live on matomo-org/plugin-LogViewer and innocraft/plugin-UsersFlow: a manual dispatch resolved the default branch, dispatched the build on the other one, and that build completed green attributed to that branch — which is what the plugin build dashboard's per-branch badges read.

Issue No

No GitHub issue.

Steps to Replicate the Issue

1. Note that this repository's default branch is 6.x-dev, so the matomo-tests.yml cron only ever fires there.
2. Expected result: the other maintained dev branch is built weekly too.
3. Actual result: it has had no scheduled build since the default branch changed.

Checklist

• [✔] Tested locally or on demo2/demo3?
• [NA] New test case added/updated?
• [NA] Are all newly added texts included via translation?
• [NA] Are text sanitized properly? (Eg use of v-text v/s v-html for vue)
• [NA] Version bumped?
• [✔] I have understood, reviewed, and tested all AI outputs before use
• [✔] All AI instructions respect security, IP, and privacy rules
• [NA] Documentation updated?