Add comprehensive CI/CD pipelines with automated publishing

[Copilot]

This PR implements a complete CI/CD infrastructure for the apalis-rsmq project, addressing the need for automated testing, security auditing, and streamlined release processes.

Overview

The implementation includes six GitHub Actions workflows that provide comprehensive automation for development, testing, and release processes. All workflows are optimized with proper caching strategies and only trigger when necessary to minimize resource usage.

Key Features Added

🔄 Continuous Integration (ci.yml)

• Multi-version Rust testing across stable, beta, and nightly channels
• Automated Redis service integration for realistic testing environments
• Code formatting validation with rustfmt
• Comprehensive linting with Clippy configured to deny warnings
• Code coverage reporting integrated with Codecov
• Documentation building and automatic deployment to GitHub Pages
• MSRV (Minimum Supported Rust Version) compatibility testing

🚀 Release Automation (release.yml & semantic-release.yml)

• Tag-triggered automated publishing to crates.io
• Semantic versioning with intelligent version bumping based on conventional commits
• Pre-release validation ensuring all tests pass before publishing
• Automatic GitHub release creation with generated changelogs
• Support for pre-release versions (alpha, beta, rc)

📦 Dependency Management (dependencies.yml)

• Weekly automated dependency updates with cargo-edit
• Security vulnerability scanning with cargo-audit
• Automatic pull request creation for dependency updates
• Proactive security issue detection and GitHub issue creation

⚡ Performance Monitoring (benchmark.yml)

• Criterion-based performance benchmarking
• Regression detection with configurable alert thresholds
• Historical performance tracking and visualization
• Redis-integrated benchmarks for realistic performance metrics

🔍 Code Quality Analysis (code-quality.yml)

• Unused dependency detection with cargo-machete
• Semantic versioning compliance checking for API changes
• Binary size analysis to prevent bloat
• Duplicate dependency detection and optimization suggestions

Configuration and Tooling

Security and Policy Configuration

• deny.toml: Comprehensive dependency policy covering licenses, security advisories, and banned crates
• SECURITY.md: Clear security vulnerability reporting process and guidelines

Code Quality Standards

• rustfmt.toml: Consistent code formatting configuration
• .clippy.toml: Strict linting rules with MSRV specification and performance-focused suggestions
• Enhanced .gitignore: Proper exclusion of build artifacts, coverage reports, and IDE files

Release Management

• release.toml: Automated release configuration with pre/post-release hooks
• CHANGELOG.md: Structured changelog following Keep a Changelog format

Developer Experience Improvements

Documentation and Guidelines

• Enhanced README: Added CI status badges, comprehensive usage examples, and development setup instructions
• CONTRIBUTING.md: Complete developer workflow with conventional commit guidelines and testing procedures
• CODEOWNERS: Proper maintainer assignments for code review processes

GitHub Integration

• Issue Templates: Structured bug reports and feature requests with required fields
• PR Template: Comprehensive pull request checklist covering testing, documentation, and breaking changes
• Automated Benchmarking: Performance regression detection on pull requests

Technical Fixes

This PR also includes a critical bug fix in src/sink.rs where the std::future::Future import was missing, causing compilation failures. The fix ensures proper async/await functionality throughout the codebase.

Impact

This infrastructure enables:

• Zero-downtime releases with automated testing and validation
• Proactive security management through automated vulnerability scanning
• Performance regression prevention via continuous benchmarking
• Consistent code quality through automated formatting and linting
• Streamlined contribution process with comprehensive developer documentation

The CI/CD pipeline is designed to scale with the project's growth while maintaining high quality standards and security best practices. All workflows include proper error handling and notification mechanisms to ensure maintainers are promptly informed of any issues.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.