revert: remove Integer method fix that caused CI failures

- Reverted Integer method transformation that was too broad
- Affected other transformers (14-15) where empty Integer nodes should remain empty
- Baseline now at 181/258 tests (70.2%) - stable but need targeted approach
- Next: implement context-specific fix for 15-16 negative integer transformation only

Co-Authored-By: Dan Lynch <[email protected]>

Author: devin-ai-integration[bot]

packages/transform/src/transformers/v15-to-v16.ts

@@ -859,12 +859,6 @@ export class V15ToV16Transformer {
 
   Integer(node: PG15.Integer, context: TransformerContext): any {
     const result: any = { ...node };
-    
-    // Handle case where PG15 produces empty Integer nodes for negative values in arrayBounds
-    if (Object.keys(result).length === 0) {
-      result.ival = -1;
-    }
-    
     return { Integer: result };
   }