Support global lookup of symbols within scopes (namespaces, outer classes, etc.) on Windows

[sanketj]

The DbgObject.global API takes a scope parameter; however, it is currently ignored on Windows. With the latest compiler changes affecting Chromium symbols like g_frame_map, the scope now needs to be considered when querying for symbols on Windows. To that end, this change adjusts the symbol name to include the scope prefix before querying the debugger/symbol files on Windows.

There is an additional complication that needs to be addressed to handle anonymous namespaces correctly. On Linux, an anonymous namespace is annotated as (anonymous namespace), whereas on Windows, it is annotated as `anonymous namespace'. To handle this discrepancy, the DbgObject.global API now takes an array of scope strings (ordered [outermost scope, ..., innermost scope]), and within this array, an anonymous namespace is simply written as "anonymous namespace". Then, this scopes array will be transformed into a scope prefix string, with the Linux/Windows specific code resolving anonymous namespaces in platform-specific ways.

[cbiesinger]

Ah I didn't know the DIA API lets you query with scopes like this!

Do you know why the old way stopped working?

Wasn't able to find the exact change, but almost certainly a Windows compiler update. The g_frame_map symbol on newer builds is prefixed with the scope, but wasn't previously.

Also, do we still need the typeName as well, now that scopes work on Windows?

IIRC, the scenario for typeName was that if multiple symbols of the same name are found, then the typeName allows us to know which one to pick. So, I think it is still needed alongside scope.