feat(targets): write generated.entitlements to ios/ instead of source

[lars-deploy-bot]

Summary

When the entitlements field is set in an expo-target.config, the generated.entitlements file is now written to ios/<productName>/generated.entitlements (the prebuild output) instead of the target's source directory. CODE_SIGN_ENTITLEMENTS is pointed at that location inside configureTargetWithEntitlements.

This keeps the target's source folder free of derived artifacts that previously needed to be either committed or .gitignore-d. The same approach was applied to Info.plist in #189.

Behavior matrix

User has config entitlements	Hand-written *.entitlements in source	Result
Yes	No	Generated file at ios/<productName>/generated.entitlements, source dir untouched
Yes	Yes	Generated file at ios/<productName>/generated.entitlements. Source file is now left untouched (previously it was overwritten) — log line tells the user it's safe to delete
No	Yes	Unchanged — existing hand-written file is used directly
No	No	No entitlements file, CODE_SIGN_ENTITLEMENTS removed (unchanged)

configureTargetWithEntitlements checks for ios/<productName>/generated.entitlements first and falls back to globbing the source target directory, so the hand-written-only flow still works.

Files

• packages/apple-targets/src/with-widget.ts — write the merged entitlements JSON to the prebuild ios/ folder; log instead of overwriting any hand-written file
• packages/apple-targets/src/with-xcode-changes.ts — `configureTargetWithEntitlements` prefers the generated file under `ios/`, falls back to source-dir glob
• packages/apple-targets/README.md — documents the new location, the source-folder-stays-clean semantics, and the precedence between config and hand-written files

Test plan

• `bunx tsc --noEmit` in `packages/apple-targets`
• `bunx jest --no-watch` in `packages/apple-targets` (8/8 pass — the entitlements path isn't covered by unit tests yet)
• Manual: target with config-driven entitlements → confirm `ios//generated.entitlements` is generated and `CODE_SIGN_ENTITLEMENTS` points at it; confirm source target dir contains no `generated.entitlements`
• Manual: target with no config entitlements but a hand-written `foo.entitlements` in source dir → confirm Xcode still uses it (CODE_SIGN_ENTITLEMENTS = `/foo.entitlements`)
• Manual: re-run `expo prebuild --clean` — file is regenerated correctly
• Manual: target with both hand-written file AND config entitlements → confirm hand-written file is left untouched, `ios/` file is used, log line appears
• e2e build (requires macOS + Xcode)

🤖 Generated with Claude Code

[Bram-dc]

I thought this would be nicer. I use env variables in my config file so the entitlements file kept changing in the tracked git commits.