Re-evaluate branch provisioning on synchronize, not only at PR open

What happens today The GitHub integration decides whether a pull request touches the schema once, at around PR-open time. If the opening commit changes nothing under supabase/, the PR is marked ignored — and a migration added in a *later* commit doesn't trigger provisioning. The bot states the behaviour in each comment it posts: tasks run on every commit, but only new migration files are pushed, and the suggested remedy is to close and reopen the pull request. What I observed On a private repo using Git-based branching, two PRs on the same day: - PR A — opening commit touched no supabase/ file. The bot commented about 80 seconds later that the PR was ignored, no changes detected in the supabase directory. About an hour after that, a later commit added a real migration under supabase/migrations/. The bot's comment had identical created_at and updated_at — never re-posted or edited — and list_branches on the parent project showed no branch for that PR more than…