Wait up to 10 minutes for npm to expose a published release

[janicduplessis]

The Release workflow's registry check after npm publish gave up after 12 × 10 s (about 2 minutes). For v0.2.0 that was too short: npm accepted the publish at 19:11:21 UTC but only exposed the version a few minutes later, so the run failed although the publish had succeeded (run):

19:11:21 npm notice Your package is being processed and may take a few minutes to become available.
19:11:21 + react-native-reserved-regions@0.2.0
19:13:25 Registry verification failed.

The registry records the 0.2.0 publish time as 19:14:29 UTC (npm view react-native-reserved-regions time), about 3 minutes after npm accepted it.

This raises the loop to 60 × 10 s (about 10 minutes). The check itself is unchanged. RELEASE.md's Recovery section gets one entry for this case: query the registry first. Once the version is visible, rerunning the workflow only re-verifies it, because it skips an existing version.

Test plan

• No release was run. The only change is the loop bound. The failure it addresses is the run linked above.