CI: restrict push trigger to main/dev to avoid duplicate runs on PRs

python-test.yml and examples.yml declared both 'on: push' and 'on: pull_request'
with no branch filter, so a push to a PR branch triggered each workflow twice
(once for push on the branch HEAD, once for pull_request on the merge commit).
Filtering the push trigger to [main, dev] (matching performance-test.yml) means
feature-branch pushes run only the pull_request instance.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: Clare72

.github/workflows/examples.yml

@@ -1,7 +1,9 @@
 name: Test VFBquery Examples
 on:
   push:
+    branches: [ main, dev ]  # avoid a duplicate run on PR-branch pushes (the pull_request event already covers those)
   pull_request:
+    branches: [ main, dev ]
   workflow_dispatch:  # Enables manual triggering
   schedule:
     - cron: '0 0 1 * *'  # Runs at 00:00 UTC on the 1st day of every month

.github/workflows/python-test.yml

@@ -2,7 +2,9 @@ name: Python Package using Conda
 
 on:
   push:
+    branches: [ main, dev ]  # avoid a duplicate run on PR-branch pushes (the pull_request event already covers those)
   pull_request:
+    branches: [ main, dev ]
   workflow_dispatch:  # Enables manual triggering
   schedule:
     - cron: '0 0 2 * *'  # Runs at 00:00 UTC on the 2nd day of every month