fix: correct malformed private field type in multiple package.json files

[dill-lk]

Overview

While auditing the React monorepo for metadata compliance, I discovered that multiple package.json files were using a string "true" for the private field instead of the boolean true required by the npm specification.

Changes

This PR corrects the private field type from string to boolean in the following locations to ensure consistency and prevent failures in automated package metadata scanning tools:

1. packages/react-devtools-fusebox/package.json
2. compiler/packages/react-forgive/client/package.json
3. compiler/packages/react-forgive/server/package.json

Impact

Malformed metadata often causes failures in security, license, and compliance scanning tools (such as ScanCode.io) that strictly validate package metadata types. This fix ensures the repository remains compliant with industry-standard package specifications.

Verification

• Audited all package.json files in the monorepo using grep.
• Verified that the private field is now correctly recognized as a boolean.

[dill-lk]

Since PR #35802 has been updated to cover all the malformed fields I identified during my audit, I am closing this PR to avoid duplication. Glad to see the entire monorepo is getting fixed!