refactor: Consolidate Message Scrolling & other Logic to Custom Hooks 🔄

[danny-avila]

Summary

I've made significant changes to improve the message scrolling functionality. My main motivation was to eliminate unnecessary prop drilling and the direct invocation of the ScrollToBottom method scattered across different components. ScrollToBottom was being called on each message render; while not a performance blocker, it was unnecessary and added confusing intermingling of logic.

To achieve this, I created a custom hook useMessageScrolling that centralizes all scrolling logic. Additionally, I introduced useMessageHelpers, a new hook dedicated to housing message utilities and abstracting logic away from the main Message component. These changes not only lead to cleaner code and enhanced maintainability, but will pave the way for virtualization in a later update.

With the growing number of custom hooks, I am starting to organize these as subfolders in the hooks directory with this update.

Ensured all scrolling behavior works as before.

Change Type

• New feature (non-breaking change which adds functionality)
• Refactor (non-breaking change which optimizes code)

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• I have made pertinent documentation changes
• My changes do not introduce new warnings
• I have written tests demonstrating that my changes are effective or that my feature works
• Local unit tests pass with my changes