Inefficient message history implementation

[harperreed]

Problem

The history functionality has several efficiency issues:

• The getMessages function in storageUtils.ts loads all messages into memory and then filters/paginates them
• Large message histories could cause performance issues on low-end devices
• Each message deletion requires reloading the entire message list
• The favorites filtering is handled in client-side code rather than in the storage utility

Impact

Poor performance with large message histories, especially on mobile devices.

Acceptance Criteria

• Implement efficient pagination in storage layer
• Add server-side filtering for favorites
• Optimize message deletion operations
• Add lazy loading for message history
• Test with large datasets (1000+ messages)

Priority

Medium - affects performance with heavy usage