ci: prevent workflows from running when triggered by github-actions bot

[plusplusoneplusplus]

Summary

Add condition to prevent GitHub Actions workflows from running when triggered by the github-actions[bot] user to prevent infinite loops and unnecessary runs from automated processes.

Changes Made

• extension-ci.yml: Added if: ${{ github.actor != 'github-actions[bot]' }} to the test job
• tests.yml: Added if: ${{ github.actor != 'github-actions[bot]' }} to the test job

Technical Details

This change prevents both CI workflows from executing when the triggering actor is github-actions[bot], which commonly occurs when:

• Automated version bumps are pushed
• Other automated workflows push commits
• Bot-generated pull requests are created

Benefits

• ✅ Prevents infinite loop scenarios with automated workflows
• ✅ Reduces unnecessary CI resource usage
• ✅ Maintains normal workflow execution for human-triggered events
• ✅ Simple, targeted solution with minimal impact

Testing

• Pre-commit hooks passed successfully
• Changes are minimal and focused on workflow control logic
• No impact on actual test execution when triggered by humans

Related Issues

This addresses potential workflow conflicts when automated processes trigger CI pipelines unnecessarily.

---

Created with GitHub Copilot