[Feat]: investigate "newer" AccessibilityNodeInfo's possibility in uia2 or espresso

[KazuCocoa]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Context: #15138 (comment)

I found that https://developer.android.com/reference/kotlin/androidx/compose/ui/semantics/package-summary#(androidx.compose.ui.semantics.SemanticsPropertyReceiver).testTag() addressed:

For newer AccessibilityNodeInfo-based integration test frameworks, it can be matched in the extras with key "androidx.compose.ui.semantics.testTag"
For legacy AccessibilityNodeInfo-based integration tests, it's optionally exposed as the resource id if testTagsAsResourceId is true (for matching with 'By.res' in UIAutomator).

Current UIA2 driver/server depends on https://developer.android.com/reference/android/view/accessibility/AccessibilityNodeInfo , so it is the "legacy" one. I wondered if the "newer" one was androidx.view.accessibility.AccessibilityNodeInfoCompat in https://developer.android.com/reference/androidx/core/view/accessibility/package-summary.

For example, extras in UIA2 had androidx.view.accessibility.AccessibilityNodeInfoCompat.SPANS_START_KEY=[]. It had androidx.view.accessibility.AccessibilityNodeInfoCompat, thus at least, https://developer.android.com/reference/androidx/core/view/accessibility/AccessibilityNodeInfoCompat was a relevant library from the composer.

https://developer.android.com/reference/androidx/core/view/accessibility/AccessibilityNodeProviderCompat has a method named createAccessibilityNodeInfo to return AccessibilityNodeInfoCompat thus it is potentially the "newer" accessibility node info...?

Then, can we use the andriodx's accessibility package for uia2 driver/server? For example like espresso server's compose/espresso, the uia2 also can switch them with legacy and new. The new is for compose based application.

Describe the solution you'd like

I don't have any idea right now if the above is achievable/correct, just found the above description when I dug into #15138 (comment) for hetpack compose.

This may not work possibly

[KazuCocoa]

https://github.com/chromium/chromium/blob/main/docs/accessibility/browser/android.md

AccessibilityNodeInfo
AccessibilityNodeInfoCompat

These would help to catch up with them, I guess. I haven't read well yet.