fix: Implement retry logic for database connection and user fetching

[Harsh-Microsoft]

Purpose

This pull request introduces retry mechanisms with exponential backoff and timeout handling for database connections in the backend and API calls in the frontend. These changes aim to improve the resilience of the application by handling transient failures more gracefully.

Backend Improvements for Resilient Database Connections:

• src/App/backend/services/sqldb_service.py:
  • Added a retry mechanism with exponential backoff for the get_connection function, allowing up to 5 attempts with an initial delay of 2 seconds between retries. The delay doubles with each failed attempt. [1] [2]
  • Imported the time module to enable the use of time.sleep for retry delays.

Frontend Improvements for API Call Resilience:

• src/App/frontend/src/api/api.ts:
  • Introduced a retry mechanism with a single retry attempt and a 5-second delay for the getUsers function. This ensures that transient errors during API calls are retried before failing.
  • Added a timeout of 60 seconds to the fetch request using AbortSignal.timeout to prevent indefinitely hanging requests.

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information

[github-actions]

🎉 This PR is included in version 1.8.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀