UIA API versioning

[codeofdusk]

Description of the new feature/enhancement

Since its initial implementation, UIA in conhost has had various levels of completeness and bugginess. To account for this, NVDA must slightly change its behaviour for the various versions. Selected examples:

• Before Refactor UiaTextRange For Improved Navigation and Reliability #4018, a number of workarounds were necessary as the ends of ranges were not always exclusive. After this PR, those workarounds were not needed, but behaviour needed to change as not all lines ended in a newline character.
• Before UIA: Fix GetVisibleRanges() and add Tracing #4495, GetVisibleRanges was unreliable.
• After Properly handle and test "end of buffer" in UiaTextRange #6986, NVDA might no longer need to use GetVisibleRanges in some cases to bound the console, as the thousands of empty lines will be removed from UIA.

Historically, NVDA has checked the Windows build number to determine which workarounds were needed. However, since newer OpenConsole can be run on older Windows, this is no longer sufficient. NVDA should be able to check which version of conhost is in use, perhaps by an API version (incremented for breaking UIA changes) in the automation ID for the text area.

Proposed technical implementation details (optional)

• The automation ID is set in ScreenInfoUiaProviderBase::GetPropertyValue().
• Note: You might consider localizing the name set in this function. NVDA specifically ignores the console's name (as it isn't localized and unnecessary for us), but other screen readers (such as Narrator) might not.

[DHowett]

Is this a common way to version UIA support in an application? I'd rather not do something strange that nobody else does here...

[DHowett]

We also do not officially recommend running OpenConsole anywhere but "on your dev machine, for a short period of time". It's not supported and likely won't be until a while after #7414 lands in the OS.

[codeofdusk]

The docs say:

An AutomationId is not necessarily guaranteed to be stable across different releases or builds of an application.

If not the AutomationId, how then can we detect different builds of the console?

For whatever it's worth, @carlos-zamora and I discussed this (offline) and he supported the idea...

[DHowett]

I wrote up a few of my thoughts on the versioning issue here: nvaccess/nvda#11796 (comment)

In short, Joseph suggests that we shouldn't use the automation ID for a version, and I explain a little bit about our philosophy on conhost/openconsole versioning.

I'm gonna reject this one for now, but as always I am willing to hear more info on it 😄