docs: update announceForAccessibility with queue

[peterc1731]

This PR adds documentation for announceForAccessibilityWithOptions, added in facebook/react-native#32637

[netlify]

✅ Deploy Preview for react-native ready!

Name	Link
🔨 Latest commit	f58d26d
🔍 Latest deploy log	https://app.netlify.com/sites/react-native/deploys/62457de8c543a600087097a3
😎 Deploy Preview	https://deploy-preview-2862--react-native.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[yungsters]

@Simek — Logistical question… when facebook/react-native#32637 is merged, do I need to wait before merging this?

[Simek]

@yungsters Depends on the timeframe, every case need an individual approach. Sometimes you need to wait even for the publish of next release, if upcoming version branch has been already cut, and PR has been merged only on main.

This is because next doc should always reflect the state of next release (0.67 ATM), so additional or future changes need to wait until next will become the docs for their target release.

[yungsters]

So the PR has been merged to main, but 0.67 has already been cut. That means I have to wait until 0.67 is released before I can merge this, right?

cc @lunaleaps, @rachelnabors - This is an interesting point of coordination friction that can also lead to outdated docs, relevant to our discussion about keeping reference docs more up-to-date.

[peterc1731]

I've updated this to reflect the changes made when facebook/react-native#32637 was merged

[Simek]

Oh, it looks like this PR, slip through and was not merged after 0.67 release, sorry about that!

@peterc1731 Can you backport the change also to the 0.68 docs file?

[Simek]

I have updated the docs for 0.68, so this should b ready to ship.

Thank you @peterc1731, for the update in the first place! 👍