fix: button state reset on switching models

[louis-jan]

Describe Your Changes

This PR resolved the issue where switching to a new button would cause the stop button to disappear.

Changes made

This pull request includes several changes to improve state management and streamline the codebase in the web directory. The changes focus on the use of Jotai atoms for state management, the addition of new utility atoms, and the removal of redundant code.

State Management Improvements:

• web/containers/Providers/ModelHandler.tsx: Replaced the use of useAtom with useAtomValue for subscribedGeneratingMessageAtom to simplify state retrieval.
• web/helpers/atoms/Thread.atom.ts: Added isWaitingForResponseAtom and isBlockingSendAtom to manage thread states and reduce unnecessary re-renders.

Utility Atom Additions:

• web/helpers/atoms/Thread.atom.ts: Introduced resetThreadWaitingForResponseAtom and resetGeneratingResponseAtom to reset thread states and generating states.

Code Simplification:

• web/screens/Thread/ThreadCenterPanel/ChatBody/index.tsx: Replaced multiple state checks with isBlockingSendAtom to streamline the logic for blocking send operations. [1] [2] [3]
• web/screens/Thread/ThreadCenterPanel/ChatInput/index.tsx: Removed redundant state checks and replaced them with isBlockingSendAtom for cleaner code. [1] [2] [3]

Test Updates:

• web/hooks/useCreateNewThread.test.ts: Removed unnecessary assertions for mockSetAtom calls to focus on essential test validations. [1] [2] [3]

[github-actions]

This is the build for this pull request. You can download it from the Artifacts section here: Build URL.