fix(v2): select correct tab when items are incorrectly ordered

[armano2]

Motivation

fixes #4465

Have you read the Contributing Guidelines on pull requests?

yes

Test Plan

create md(x) file in project with

import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

<Tabs values={[ {label: 'Android', value: 'android'}, {label: 'iOS', value: 'ios'}, {label: 'Web', value: 'web'}, ]}>
  <TabItem value="web">Web</TabItem>
  <TabItem value="android">Android</TabItem>
  <TabItem value="ios">iOS</TabItem>
</Tabs>

currently there is no component gallery or place where specific test can be added

simple regression test can be done by checking: https://deploy-preview-4468--docusaurus-2.netlify.app/docs/typescript-support

[netlify]

[V1] Deploy preview failure

Built without sensitive environment variables with commit a504a80

https://app.netlify.com/sites/docusaurus-1/deploys/60549e4053745d0008f2fcaf

[armano2]

we actually wants to use currentTarget here, instead of target
In case if tab header is not simple element (eg. swizzled) this will stop working

target: is the element that triggered the event (e.g., the user clicked on)
currentTarget: is the element that the event listener is attached to.

https://developer.mozilla.org/en-US/docs/Web/API/Event/currentTarget

[netlify]

Deploy preview for docusaurus-2 ready!

Built without sensitive environment variables with commit a504a80

https://deploy-preview-4468--docusaurus-2.netlify.app

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🟠 Performance	77
🟢 Accessibility	96
🟢 Best practices	100
🟢 SEO	100
🟢 PWA	95

Lighthouse ran on https://deploy-preview-4468--docusaurus-2.netlify.app/

[armano2]

instead of checking childrens we should check values, this also solves crash with missing TabItem during development

[slorber]

Seems to work fine! thanks