Move to use Cswin32 IAccessible

[lonitra]

Related: #9795

• Converts IAccessibleEx and ILegacyIAccessibleProvider to Cswin32 definition in dedicated commits
• Introduce ComSafeArrayScopeExtensions which provides a way to generically get Safe array scope of corresponding COM pointers given an array of COM interfaces.
• Move to use Cswin32 IAccessible:
  • Adds a few new internal virtual APIs to avoid excessive allocations by changing between managed and native types e.g. BSTR <-> string, IDispatch <-> AccessibleObject.
    CanXDirectly > Determines whether native type should be grabbed directly since it avoids new allocations
    GetXInternal() > Grabs the native type of interest
    The idea is that our internal objects should not need to move between native and managed types so much. They should use the native types all the way through if they can. Objects that overrides our public facing IAccessible properties/methods (e.g. Parent, GetSelected()`) need to be checked for whether they are subclassed, if they are not then this is another chance where we can avoid allocations by using the optimized path (native types).
• Add IManagedWrapper to AccessibleObject
• Fix tests, tests required more mock setup due to newly added internal methods.

Microsoft Reviewers: Open in CodeFlow

[JeremyKuhne]

Few initial comments, spoke offline.

[JeremyKuhne]

One could also check the string name of the module against the known name of the design assembly if that helps.

[JeremyKuhne]

Very nice! Added a few comments.

[JeremyKuhne]

Awesome work, @lonitra!