fix: fetch history on button click and not on web page load

[Harsh-Microsoft]

Purpose

This pull request includes several changes to improve the chat functionality and refactor how chat history is fetched in the application. Chat History is being fetched only when the user clicks on the history button and not on the web page load, which in turn doesn't block the chat interface.
AB#15563

Improvements to chat functionality:

• frontend/src/pages/chat/Chat.tsx: Added fallback logic to use currentChat if a conversation is not found in chatHistory when fetching a conversation by ID. [1] [2] [3] [4]

Refactoring chat history fetching logic:

• frontend/src/pages/layout/Layout.tsx: Updated handleHistoryClick to fetch chat history if not already loaded and added a new fetchChatHistory function to handle the fetching process.
• frontend/src/state/AppProvider.tsx: Removed the fetchChatHistory function from the useEffect in AppStateProvider and refactored the logic to update the chat history loading state based on the response from historyEnsure.

Import updates:

• frontend/src/pages/layout/Layout.tsx: Added imports for Conversation, historyList, and ChatHistoryLoadingState from ../../api.

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

• I have built and tested the code locally and in a deployed app
• For frontend changes, I have pulled the latest code from main, built the frontend, and committed all static files.
• This is a change for all users of this app. No code or asset is specific to my use case or my organization.

Other Information

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀