[Copilot]

Description

Addresses Dependabot alerts by bumping react-native, react-native-macos, and react-native-windows to the latest supported versions in the example apps. The change is limited to yarn.lock. The existing package.json ranges already cover the new versions.

Package	Workspace	Before	After
react-native-macos	example-macos	0.81.9	0.81.9 (unchanged; latest supported)
react-native	example-macos	0.81.6	0.81.6 (unchanged; pinned by rn-macos)
react-native	example-windows	0.83.9	0.83.10
react-native-windows	example-windows	0.83.0	0.83.3
@react-native/* (0.83 line)	example-windows	0.83.9	0.83.10
@react-native-windows/*	example-windows	0.83.0	0.83.1–0.83.3
@react-native-windows/find-dotnet-tools	example-windows	—	0.0.0 (new dependency of rnw 0.83.3)

In the lockfile, rnw's @react-native/*@^0.83.4 entries were tied to react-native's exact 0.83.9 entries. A plain yarn up would have left duplicate copies, so I deleted all 0.83 RN/RNW entries and regenerated them.

Also fixes two high-severity advisories in transitive dependencies (in-range updates):

• follow-redirects 1.16.1 → 1.16.2 (GHSA-mrwp-f3q8-3g9p)
• joi 17.13.8 → 17.13.9 (GHSA-4528-x5fx-h6hg)

The remaining yarn npm audit findings (glob, minimatch, deepmerge) either have no patched version or are only patched in a new major version outside the current ranges.

Platforms affected

• Android
• iOS
• macOS
• visionOS
• Windows

Test plan

• yarn dedupe --check: passed (no packages can be deduped)
• yarn install --immutable: passed
• Every new version is older than the npmMinimalAgeGate of one week
• yarn npm audit --all --recursive: follow-redirects/joi advisories no longer reported
• CI should build example-windows