Improve error handling & network resilience in contact form AJAX submission

Team 101

->What’s the issue?

The contact form currently submits using jQuery AJAX, but the error handling is quite minimal.
Right now, if something goes wrong (like a slow server, network issue, or unexpected response), the user only sees a very generic message. There’s no clear distinction between different types of failures such as:
- Server errors (500)
- Missing endpoint (404)
- Request timeout
- Network connectivity problems

Also, there is no timeout configured, so if the server hangs, the user might be left waiting without proper feedback.

- >Why this matters

The contact form is an important interaction point on the website. If it fails silently or shows unclear messages, it can confuse users and reduce trust in the platform.

Better error handling would:

- Provide clearer feedback to users
- Prevent indefinite waiting
- Make debugging easier during development
- Improve overall reliability

->Proposed improvement

Enhance the existing `$.ajax()` configuration in `js/main.js` by:

- Adding a timeout to the request
- Differentiating error messages based on failure type
- Logging meaningful error details in the console
- Handling unexpected server responses more gracefully

This would not change the success flow — it would only improve behavior when something goes wrong.

I’d like to work on implementing this improvement.

Start in js/main.js by locating the contact form's $.ajax() configuration and reading its current failure path. Add the requested timeout and distinct handling for server errors, missing endpoints, timeouts, network failures, and unexpected responses while preserving the success flow. Done means users receive clear feedback and useful error details are logged without indefinite waiting.

Written by the indexing model from the issue text.