MS Word with UIA: use custom extensions to support line number, layout column number and section number

[michaelDCurran]

Link to issue number:

None.

Summary of the issue:

When supporting Microsoft word via UI automation, up to now there was no way to report line numbers, layout column numbers or section numbers. This was because these concepts do not exist in the UI Automation standard.
However, Microsoft recently added custom patterns to UI automation, as a part of its Custom Extensions work, which included custom properties and custom annotations.
Microsoft word has now added its own custom pattern which allows fetching information from a text range, such as line number, layout column number and section number.

Description of how this pull request fixes the issue:

Using the microsoft/microsoft-ui-uiautomation Remote Operations library, fetch line number, layout column number and section number in Microsoft word.
Note that the Remote Operations library is only supported in Windows 11 and above, and the custom pattern in Microsoft Word is only available as of build 16.0.14725.

A part from adding support for these specific attributes, this PR also acts as a first commit to add integrations with the UI Automation Remote Operations library. Now that we are building and including this library, there is much more code that can eventually be remoted for a massive speedup.

Testing strategy:

• Opened a document in Microsoft word
• Turned on reporting of line numbers in NVDA's document formatting settings
• Moved up and down the document with the arrow keys, ensuring that NVDA spoke the current line number before the content of the line.
• Ensured report pages was turned on in NVDA's document formatting settings.
• Set up the document in 2-column layout, and inserted a column break in the content.
• used the arrow keys to move between the two columns, ensuring that the column number is announced as it changes.

Known issues with pull request:

None known.

Change log entries:

New features
Changes
Bug fixes
For Developers

Code Review Checklist:

• Pull Request description:
  • description is up to date
  • change log entries
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• API is compatible with existing add-ons.
• Documentation:
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English

[AppVeyorBot]

• Build execution time has reached the maximum allowed time for your plan (60 minutes).

See test results for failed build of commit 61e47fbed5

[feerrenrut]

There are a few build warnings introduced, these may be outside your control, but it would be good if they were silenced:

"C:\work\repo\nvda\PR\include\microsoft-ui-uiautomation\src\uiAutomation\microsoft.ui.uiautomation\Microsoft.UI.UIAutomation.vcxproj" (Build target) (1) ->
(PrepareForBuild target) ->
  C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppBuild.targets(499,5): warning MSB8004: Output Directory does not end with a trailing slash.  This build instance will add the slash as it is required to allow proper evaluation of the Output Directory. [C:\work\repo\nvda\PR\include\microsoft-ui-uiautomation\src\uiAutomation\microsoft.ui.uiautomation\Microsoft.UI.UIAutomation.vcxproj]

[michaelDCurran]

@feerrenrut I believe I have addressed all your points.

[feerrenrut]

I'll leave it up to you about this, I think the C++ standard library approach is less error prone and sets a good example.

[AppVeyorBot]

• PASS: Translation comments check.
• PASS: Unit tests.
• PASS: Lint check.
• FAIL: System tests. See test results for more information.
• Build (for testing PR): https://ci.appveyor.com/api/buildjobs/yi1lprju4flchxlp/artifacts/output/nvda_snapshot_pr13283-24682,bf6ff0d7.exe

See test results for failed build of commit bf6ff0d7ba

[feerrenrut]

The test failure looks unrelated. I have kicked off the build again.
Old build link: https://ci.appveyor.com/project/NVAccess/nvda/builds/42592615/tests