💡 What
Refactored multiple readFileSync calls in packages/pod-install/src/index.ts and packages/expo-brownfield/plugin/src/common/filesystem.ts to pass the 'utf8' encoding string directly to the function, instead of calling .toString() on the returned Buffer.

🎯 Why
Calling readFileSync(path).toString() first allocates a Buffer object in memory and then converts it to a string. By passing the encoding directly (readFileSync(path, 'utf8')), Node.js handles the decoding internally within C++ and returns the string directly to JavaScript. This is a micro-optimization that reduces memory allocation overhead and garbage collection pressure, particularly when reading files repeatedly or traversing hierarchies.

📊 Impact

• Reduces unnecessary intermediate buffer allocations.
• Small decrease in memory footprint during file reads.
• Decreases garbage collection overhead.

🔬 Measurement

• Run yarn --cwd packages/pod-install lint and yarn --cwd packages/pod-install jest --passWithNoTests
• Run yarn --cwd packages/expo-brownfield lint and yarn --cwd packages/expo-brownfield jest --passWithNoTests
• Verification confirmed that no regressions were introduced by this change.

PR created automatically by Jules for task 14972420639588682777 started by @vishnu-madhavan-git