feat: tabs now support deep-linking

[blakef]

Adds support for deep-linking in tabs. This will only work after #3618 goes it (note: it won't break anything if it does land before).

I updated all of these using this:

git grep -lE '<Tabs .*groupId' | xargs -J echo gsed -ri 's/<Tabs(.*)groupId="([^\"]*)"/<Tabs\1groupId="\2" queryString/'

CleanShot.2023-03-10.at.15.52.00.mp4

[netlify]

✅ Deploy Preview for react-native ready!

Name	Link
🔨 Latest commit	f9b4550
🔍 Latest deploy log	https://app.netlify.com/sites/react-native/deploys/64122416fd4498000832f364
😎 Deploy Preview	https://deploy-preview-3619--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.

[motiz88]

1. I don't think we generally update old versioned snapshots of the docs unless necessary. Reverting those changes can help with the size of this diff.
2. This doesn't fix existing inbound links that only include fragment references (without the new query params), right?

[blakef]

Answering out of order @motiz88:

This doesn't fix existing inbound links that only include fragment references (without the new query params), right?

No it doesn't fix that, just enables updating the query string when interacting (or the page if directly linked with the query string parameters set). Interestingly there's some other work that I have to follow up with here to scroll after load & update the tabs (some of the ids aren't visible on load. That'd also be a wider docusaurus contrib (but we can swizzle it for now).

FYI our CLI has a draft PR using this react-native-community/cli#1870

I don't think we generally update old versioned snapshots of the docs unless necessary. Reverting those changes can help with the size of this diff.

The change is automated and pretty low risk (IMHO). The CLI change means we'd want to update all of our supported versions (0.71, 0.70, 0.69). The win for our DX is significant enough that I think it's worth figuring out a way to make this more digestible for review.

Maybe I can just break out next + 0.71 as part of this to decrease the review burden?

[motiz88]

lgtm, assuming you've done a spot check that the old versions still work after this change.