fix: detect preprocessor in re-exported named exports

[vivekchavan14]

Description

Fixes #6894

The TypeScript parser now correctly detects preprocessor functions that are re-exported from other modules using named exports.

Problem

Previously, users could not use:

export { preprocessor } from "./extract_user_info_from_jwt_token";

They had to use this workaround:

import { preprocessor as extractor } from "./extract_user_info_from_jwt_token";

export async function preprocessor(event: any) {
  return await extractor(event);
}

Solution

The parser now checks ExportNamed AST nodes in addition to function declarations, detecting any specifier named preprocessor.

Changes

• Modified windmill-parser-ts/src/lib.rs to detect preprocessor in named exports
• Added 4 comprehensive tests covering:
  • Simple re-export: export { preprocessor } from "./other"
  • Re-export with renaming
  • Mixed exports with multiple identifiers
  • Negative case (exports without preprocessor)

Testing

All 23 tests pass, including the new ones specifically for this fix.

cargo test
# test result: ok. 23 passed; 0 failed