feat: Add automatic semantic versioning workflow

- Create GitHub Actions workflow for automatic version bumping based on PR title prefixes
- Add version bumping script (scripts/bump_version.py) for programmatic updates
- Update PR template with semantic versioning guidelines
- Document versioning workflow in contributing guide
- Integrate with existing Docker build workflow via git tags

This enables automatic version management:
- feat: triggers MINOR version bump
- fix: triggers PATCH version bump
- breaking: triggers MAJOR version bump
- docs/chore/test: no version bump

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

.github/pull_request_template.md

@@ -1,116 +1,49 @@
-<!--
-Thank you for your contribution to the Gemini MCP Server! 
-Please provide a clear description of your changes and ensure all requirements are met.
--->
+## PR Title Format
 
-## Related Issue
+**Please ensure your PR title follows one of these formats:**
 
-<!-- Link to the issue that this PR addresses -->
-<!-- e.g., "Closes #123" or "Fixes #456" -->
-<!-- If no issue exists, please consider creating one first to discuss the change -->
-
-Closes #
-
-## Type of Change
-
-<!--
-Please check the relevant box with [x]
--->
-
-- [ ] 🐞 Bug fix (non-breaking change which fixes an issue)
-- [ ] ✨ New feature (non-breaking change which adds functionality)
-- [ ] 🛠️ New Gemini tool (adds a new tool like `chat`, `codereview`, etc.)
-- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- [ ] 📖 Documentation update
-- [ ] 🧹 Refactor or chore (no user-facing changes)
-- [ ] 🏗️ Infrastructure/CI changes
+- `feat: <description>` - New features (triggers MINOR version bump)
+- `fix: <description>` - Bug fixes (triggers PATCH version bump)
+- `breaking: <description>` or `BREAKING CHANGE: <description>` - Breaking changes (triggers MAJOR version bump)
+- `perf: <description>` - Performance improvements (triggers PATCH version bump)
+- `refactor: <description>` - Code refactoring (triggers PATCH version bump)
+- `docs: <description>` - Documentation only (no version bump)
+- `chore: <description>` - Maintenance tasks (no version bump)
+- `test: <description>` - Test additions/changes (no version bump)
+- `ci: <description>` - CI/CD changes (no version bump)
+- `style: <description>` - Code style changes (no version bump)
 
 ## Description
 
-<!--
-A clear and concise description of the changes.
-- **What** is the change?
-- **Why** is this change necessary?
-- **How** does it address the issue?
--->
+Please provide a clear and concise description of what this PR does.
+
+## Changes Made
+
+- [ ] List the specific changes made
+- [ ] Include any breaking changes
+- [ ] Note any dependencies added/removed
 
 ## Testing
 
-<!--
-The project has high testing standards. Please describe the tests you have added or updated.
-Both unit tests (no API key) and live integration tests (with API key) are important.
--->
+- [ ] Unit tests pass
+- [ ] Integration tests pass (if applicable)
+- [ ] Manual testing completed
+- [ ] Documentation updated (if needed)
 
-### Unit Tests (Required)
-- [ ] I have added new unit tests to cover my changes
-- [ ] I have run `python -m pytest tests/ --ignore=tests/test_live_integration.py -v` and all tests pass
-- [ ] New tests use proper mocking and don't require API keys
+## Related Issues
 
-### Live Integration Tests (Recommended)
-- [ ] I have tested this with a real Gemini API key using `python tests/test_live_integration.py`
-- [ ] The changes work as expected with actual API calls
-- [ ] I have tested this on [macOS/Linux/Windows (WSL2)]
+Fixes #(issue number)
 
-### Docker Testing (If Applicable)
-- [ ] I have tested the Docker build: `docker build -t test-image .`
-- [ ] I have tested the Docker functionality: `./setup-docker.sh`
-- [ ] Docker integration works with the changes
+## Checklist
 
-## Code Quality
+- [ ] PR title follows the format guidelines above
+- [ ] Code follows the project's style guidelines
+- [ ] Self-review completed
+- [ ] Tests added/updated as needed
+- [ ] Documentation updated as needed
+- [ ] All tests passing
+- [ ] Ready for review
 
-<!--
-Please confirm you've followed the project's quality standards
--->
+## Additional Notes
 
-- [ ] My code follows the project's style guidelines (`black .` and `ruff check .`)
-- [ ] I have run the linting tools and fixed any issues
-- [ ] I have commented my code, particularly in hard-to-understand areas
-- [ ] My changes generate no new warnings
-- [ ] I have updated type hints where applicable
-
-## Documentation
-
-<!--
-Documentation should be updated to reflect any user-facing changes
--->
-
-- [ ] I have made corresponding changes to the documentation
-- [ ] I have updated the README.md if my changes affect usage
-- [ ] I have updated CONTRIBUTING.md if my changes affect the development workflow
-- [ ] For new tools: I have added usage examples and parameter documentation
-
-## Breaking Changes
-
-<!--
-If this is a breaking change, please describe what breaks and how users should adapt
--->
-
-- [ ] This change is backwards compatible
-- [ ] OR: I have documented the breaking changes and migration path below
-
-<!--
-If breaking changes, describe them here:
--->
-
-## Additional Context
-
-<!--
-Add any other context about the pull request here, such as:
-- Performance implications
-- Security considerations
-- Future improvements this enables
-- Screenshots (for UI changes)
-- Related PRs or issues
--->
-
-## Checklist for Maintainers
-
-<!--
-This section is for maintainers to check during review
--->
-
-- [ ] Code review completed
-- [ ] All CI checks passing
-- [ ] Breaking changes properly documented
-- [ ] Version bump needed (if applicable)
-- [ ] Documentation updated and accurate
+Any additional information that reviewers should know.