`LongWindowOptimized` pass should select the best pre-aggr table if there are multiple

**Bug Description**
Currently the `LongWindowOptimized` pass just select the first one pre-aggr table and use it.

**Expected Behavior**
Two possible solutions:
- only create one pre-aggr table if all the meta is same expect the bucket size
- select the best pre-aggr if there are multiple pre-aggr tables exists for the same meta

Look for the LongWindowOptimized pass in the codebase, likely in a query optimizer or planner module. Identify where pre-aggregation tables are selected. Examine the metadata comparison logic to understand how to choose the 'best' table based on bucket size or other criteria. Running existing tests related to window optimization will help verify the fix.

Escrito por el modelo de indexación a partir del texto del issue.