fix(dashboard-api): handle transaction buffering timeouts

- Relaxed the isTransactionError strict check to also catch 'buffering timed out' and generic 'Session' or 'sessions are not supported' errors.
- This ensures that when MongoDB instances (e.g., standalone setups) fail to start a session due to missing replica set configuration, the transaction gracefully falls back to the non-transactional operation instead of crashing with a 500.

Author: yash-pouranik

apps/dashboard-api/src/controllers/project.controller.js

@@ -389,9 +389,12 @@ module.exports.createProject = async (req, res) => {
       session.endSession();
     }
 
-    const isTransactionError = err.message && 
-      err.message.includes("Transaction numbers are only allowed") && 
-      (err.code === 20 || err.codeName === 'IllegalOperation');
+    const isTransactionError = err.message && (
+      (err.message.includes("Transaction numbers are only allowed") && (err.code === 20 || err.codeName === 'IllegalOperation')) ||
+      err.message.includes("buffering timed out") ||
+      err.message.includes("Session") ||
+      err.message.includes("sessions are not supported")
+    );
 
     if (isTransactionError) {
       try {