Implementing caching for query

[Krishnachaitanyakc]

1. Session-Independent Query Detection (QueryNormalizer.ts:40-103)
   • Added isSessionIndependentQuery() method to identify table browsing
     queries
   • Detects simple SELECT * and basic column selection patterns
   • Excludes session-dependent functions (USER(), NOW(), etc.) and complex
     operations
2. Dual Cache Key Strategy (QueryNormalizer.ts:108-131)
   - Enhanced generateCacheKey() with conditional session logic
   - Session-independent queries: ${connectionId}:${database}
   - Session-dependent queries: ${connectionId}:${database}:${sessionId}
3. Enhanced Cache Manager (CacheManager.ts)
   - Updated methods to accept optional sessionId parameter
   - Added comprehensive logging for cache strategy monitoring
   - Enhanced metadata tracking with isSessionIndependent field
4. Database Layer Integration (base.ts:103-146, clickhouse.ts:37-61)
   - Updated BaseDatabaseManager.query() to pass sessionId to cache methods
   - ClickHouse-specific cache optimizations with longer TTL and compression
   - Maintained backward compatibility with existing cache invalidation
5. Enhanced Logging and Monitoring
   - Detailed cache hit/store logging with strategy information
   - TypeScript error fixes for proper type inference
   - Performance tracking for cache strategy effectiveness

[sahithvibudhi]

This will only save on network round trip and the queries we run to populate the tables in the left pane.

We should probably not do this because, if a user runs a INSERT statement followed by a SELECT. he would not be seeing the latest insertion

@Krishnachaitanyakc thoughts?

[Krishnachaitanyakc]

Good point, let me tweak the implementation to invalidate cache when we perform a write operation