Add GitHub Actions CI/CD workflow for automatic GitHub Pages deployment

[Copilot]

This PR adds automated CI/CD pipeline for the PerVenT.github.io personal website to enable automatic deployment to GitHub Pages whenever updates are made.

Changes Made

🚀 GitHub Actions Workflow (.github/workflows/deploy.yml)

• Automatic Deployment: Triggers on every push to the main branch
• Pull Request Validation: Tests the workflow on PRs without deploying
• Custom Domain Preservation: Maintains the CNAME file for 1.pervent.dev domain
• Static Site Optimized: Designed specifically for HTML/CSS static sites without build process
• Safe Concurrency: Prevents deployment conflicts with proper job orchestration
• Modern GitHub Actions: Uses latest stable actions (checkout@v4, configure-pages@v4, deploy-pages@v4)

📚 Documentation (.github/README.md)

• Comprehensive setup instructions for repository maintainers
• Workflow feature explanations and technical details
• GitHub Pages configuration requirements

Technical Implementation

The workflow uses a two-job approach:

1. Build Job: Checks out code, configures GitHub Pages, and uploads the static site as an artifact
2. Deploy Job: Deploys the artifact to GitHub Pages (only on main branch pushes)

This setup ensures:

• Zero-downtime deployments
• Proper GitHub Pages environment configuration
• Preservation of all static assets including custom domain settings
• No interference with existing site functionality

Setup Required

After merging this PR, the repository owner needs to:

1. Navigate to Settings → Pages in the GitHub repository
2. Change the source from "Deploy from a branch" to "GitHub Actions"
3. The next push to main will automatically trigger the deployment workflow

The website will continue to be accessible at 1.pervent.dev with no interruption to the existing functionality.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.