[Issue 2142] Clarify deployment folder generalized deploying file

[daaimah123]

📝 Description

This PR updates the deploying.md file to be platform-agnostic, removing Heroku-specific content and creating a more general deployment guide. The existing Heroku-specific content remains in deploying-to-heroku.md, while the main deployment document now covers universal deployment concepts applicable across different hosting platforms.

🔂 Changes Made

• Rewrote deploying.md to focus on platform-agnostic deployment concepts
• Renamed deploying.md to general-project-deploying.md
• Removed Heroku-specific references from the main deployment guide
• Added sections on deployment environments, CI/CD, and configuration management
• Expanded the "Common Challenges" and "Supplemental Resources" sections
• Added links to platform-specific guides (including the existing Heroku guide)
• Updated prerequisites to be more general and applicable to various deployment scenarios

⚙️ Related Issue

Issue Number: #2142

🍏 Type of Change

Topic Outline Update

🎁 Acceptance Criteria

• Content is platform-agnostic and applicable to various deployment scenarios
• Clear separation between general deployment concepts and platform-specific instructions
• Comprehensive coverage of deployment fundamentals (environments, configuration, monitoring)
• Maintains educational value for participants with different technology stacks
• Links appropriately to platform-specific guides for detailed implementation steps

🧪 How to test or what to evaluate

1. Review general-project-deploying.md file to ensure it contains no platform-specific instructions
2. Verify that all deployment concepts are explained in a general way applicable to various platforms
3. Check that links to platform-specific guides (including Heroku) are properly referenced
4. Ensure the content follows the curriculum's standard format (Projected Time, Prerequisites, etc.)
5. Validate that the learning objectives and specific things to learn align with the updated content