fix(inject-testid): skip functions with 'widget'/'worklet' directives

[joernroeder]

Summary

babel-plugin-inject-testid injects Component.displayName = "Component" onto every PascalCase function that returns JSX. When another Babel plugin in the pipeline rewrites such a function into a non-object, that assignment throws at runtime.

The concrete trigger is expo-widgets: its 'widget' directive (via babel-preset-expo) serializes the layout function into a string literal. The injected assignment then runs against a string at module-eval time:

TypeError: Cannot create property 'displayName' on string 'function(props){return _jsxs(VStack,{…})}'

Because it fires during module initialization, it aborts the module and can cascade into confusing downstream errors (in the original report, the app root failed with Cannot read property 'ErrorBoundary' of undefined).

Fix

Tag the component scope when the function body carries a 'widget' or 'worklet' directive, and skip both displayName and testID injection for those functions (their bodies are serialized/relocated, so injected testIDs wouldn't behave as expected anyway).

Applied consistently to all three implementations:

• babel-plugin-inject-testid.cjs (runtime artifact)
• src/babel-plugin-inject-testid.ts (babel-plugin source)
• src/babel/inject-testid.ts (injectTestIds transformer)

Tests

Added regression tests to src/__tests__/babel-inject-testid.test.ts:

• 'widget' directive function → no testID, no displayName
• 'worklet' directive function → no testID, no displayName
• a skipped directive function does not affect injection on sibling components

bun test src/__tests__/babel-inject-testid.test.ts → 18 pass. oxlint, oxfmt --check, and tsc --noEmit all clean.

Fixes #126