Fix: Critical Bugs, Data Integrity, and Configuration Management

[SadhanaShree25]

📝 Summary

This PR addresses several critical issues identified in the application, including data integrity bugs during task deletion, potential server crashes due to unhandled async errors, and improper environment configuration loading.

🚀 Key Changes

🛠 Backend (Core Logic & API)

• Data Integrity: Fixed a bug where deleting a task left 'dangling' references in routines. Updated the deletion logic to automatically remove the task ID from all routines when it is deleted.
• API Stability: Wrapped duplication routes in async error handlers to ensure asynchronous errors are properly caught, preventing potential server crashes.
• Architectural Cleanup:
  • Extracted ID validation into a shared middleware to standardize validation across different modules.
  • Updated routine routes to use this shared middleware.
• Configuration Security:
  • Relocated environment configuration initialization to the very beginning of the script to ensure variables are available to all modules during the import phase.
  • Removed hardcoded production URLs from CORS configuration in favor of strict environment variable usage.
• Auth Refinement: Updated authentication logic to initialize configuration variables within the request scope, ensuring they respect the loaded environment settings.

💻 Frontend (API Integration)

• Environment Isolation: Refactored API client configuration to remove hardcoded production fallbacks, ensuring the app relies strictly on environment-specific variables.

🐞 Issues Resolved

• Fixed: Task references not being cleaned up in routines upon deletion.
• Fixed: Server potential crash on duplication failure.
• Fixed: Environment configuration values being ignored in top-level module initializations.
• Improved: Code maintainability by standardizing validation middleware.

🧪 Testing Performed

• Verified task deletion correctly updates associated routines in the database.
• Verified API routes correctly handle invalid ID formats using shared middleware.
• Confirmed CORS origins are correctly read from environment variables.
• Verified frontend client connects correctly without hardcoded fallbacks."

[SadhanaShree25]

This PR includes the required changes. Please review and let me know if any modifications are needed.
@aryandas2911