Add comprehensive deployment troubleshooting documentation and diagnostic tools

[Copilot]

This PR addresses a common contributor confusion about why their changes aren't appearing on the live website after pushing to the repository. The issue stems from the repository's branch protection rules and automated deployment workflow that many contributors aren't familiar with.

Problem

Contributors frequently ask "why can't I see my new push?" when their changes don't appear on the live website. This confusion arises because:

1. Branch Protection: Direct pushes to main are blocked, requiring pull requests
2. Deployment Process: Only changes merged to main trigger the automated Quarto build and GitHub Pages deployment
3. Timing: Even after merge, deployment takes 5-10 minutes
4. Workflow Misunderstanding: Contributors may not realize they need to follow the PR workflow

Solution

This PR adds comprehensive documentation and diagnostic tools to help contributors understand and troubleshoot deployment issues:

📖 Documentation Added

• WHY_CANT_I_SEE_MY_PUSH.md: Direct answer to the most common question, explaining that previous branch pushes don't interfere with new ones
• TROUBLESHOOTING_DEPLOYMENTS.md: Comprehensive guide covering:
  • Step-by-step deployment process explanation
  • Common issues and solutions
  • Proper workflow for making changes
  • How to check deployment status

🔧 Diagnostic Tool

• check-deployment-status.sh: Interactive script that:
  • Checks current git status and branch
  • Identifies uncommitted changes
  • Shows relationship between current branch and main
  • Provides specific next steps based on current state

📝 README Updates

Enhanced the existing README with a troubleshooting section that includes:

• Quick reference to the diagnostic script
• Link to comprehensive troubleshooting guide
• Quick checklist for common issues

Key Benefits

1. Self-Service: Contributors can diagnose their own deployment issues
2. Educational: Helps contributors understand the Git workflow and deployment process
3. Reduces Support Load: Clear documentation reduces repetitive questions
4. Onboarding: New contributors get clear guidance on proper workflow

Usage Example

After making changes, contributors can simply run:

./check-deployment-status.sh

This will show their current status and provide specific next steps, such as:

📈 Your branch is 2 commits ahead of main
   Your changes will appear on the website after:
   1. Opening a pull request
   2. Merging the PR into main
   3. Waiting 5-10 minutes for deployment

The documentation directly addresses the user's specific concern about whether "another push from a different branch 20 minutes ago" affects their current push (answer: no, branches are independent).

---

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