Fix: Hide sensitive backend configuration errors from user interface

[Krishanhkr]

This PR addresses the issue of sensitive backend configuration errors being exposed directly to the end-user in the chat UI.

Changes:

• Modified the exception handling in backend/agents.py -> handle_chat method.
• Replaced the direct exception string return with a user-friendly generic error message.

Closes #95

[QuantumByte-01]

Correct fix — the generic message is appropriate and hides internal details from users.

Two notes:

1. This PR and PR #92 both modify the same exception handler in handle_chat — they will conflict. Merge one first.
2. The existing print(f"Error in handle_chat: {e}") and traceback.print_exc() remain. Consider replacing with logger.exception() in a follow-up to keep logging consistent.

[Krishanhkr]

"Thanks for the feedback!
I've updated the PR to use logger.exception() for consistent logging in
backend/agents.py

I have also synced my branch with the latest main.

Regarding the conflict with PR #92, I am happy to rebase once #92 is merged, or you can merge this one first as per your preference. Ready for another review!"

[Krishanhkr]

Hii,

I have resolved the merge conflicts and updated the PR accordingly.
All suggested changes have been implemented.

Please let me know if any further improvements are needed.
Looking forward to your feedback.