Handle Mongoose Connection Failures Gracefully

@anshkarwasra is already working on this.

Since Dec 24, 2024.

#### **Description**
Mongoose fails to connect to the database, the application does not currently handle the error, causing the app to crash unexpectedly. One common reason is that you're trying to access the database from an IP that isn't whitelisted. This leads to poor user experience on the frontend and unclear debugging information on the backend. To address this, we need to implement both frontend and backend improvements to ensure meaningful feedback, error handling and stability during database outages.

---

#### **Steps to Reproduce**
1. Stop the MongoDB server/use an invalid database URI/remove your current ip address from network access list on security tab of mongodb console.
2. Start your local server.
3. Try to access the `/api/Tickets` endpoint via the frontend.
4. Observe that the error is not handled effectively on either of the backend and frontend and the app breaks.

---

#### **Proposed Solutions**

### **1. Backend Enhancements**

- **Handle Database Connection Errors Gracefully**:
- Wrap the Mongoose connection logic in a `try-catch` block and handle connection errors.
- Provide meaningful HTTP responses to the client when a database connection fails (e.g., return `503 Service Unavailable`).

---

### **2. Frontend Enhancements**

- **Graceful Fallback UI**:
Show a user-friendly message when the backend is unable to fetch data due to database connection issues.

```javascript
// app/page.jsx

const data = await getTickets();

if (!data || !data?.tickets) {
return (

);
}

const tickets = data.tickets;
```