[cDAC] Implement basic stackwalking

[max-charlamb]

Contributes to #110758

Implements bulk of the cDAC stackwalking mechanics.

• IStackWalk contract

Supports amd64 and arm64 architectures. Tested on Windows targeting win-amd64 and linux-arm64 dumps.

Supports InlineCallFrames and SoftwareExceptionFrames.

Does not support and will be added in future PRs:

• Filtering based on CLRDataSimpleFrameType Support flags in IXCLRDataTask.CreateStackWalk #112366
• Fetching Frame names. [cDAC] Implement ClrDataAccess::GetFrameName #112274
• IXCLRDataStackWalk::Request parameters CLRDATA_REQUEST_REVISION and CLRDATA_STACK_WALK_REQUEST_SET_FIRST_FRAME [cDAC] Implement IXCLRDataStackWalk::Request support for CLRDATA_REQUEST_REVISION and CLRDATA_STACK_WALK_REQUEST_SET_FIRST_FRAME #112275
• Host platforms other than Windows amd64 Support linking native libraries to cDAC on non-Windows platforms #112416 and [cDAC] Support building and linking cross targeted cDAC unwinders on all platforms #112272

[davidwrighton]

I don't like this naming/meaning. Looking closer at this, this concept of "module" isn't used anywhere else in the documentation. Other parts of the documentation refer to modules as the IL concept, but in this case it refers to the concept of a module which is either a PE binary which holds R2R code, or a CodeHeap which may have code from many different IL modules within it. Possibly change the name here to something like "GetUnwindInfoBaseAddress" and document that it serves as the base pointer for the RUNTIME_FUNCTION found in the GetUnwindInfo api?

[max-charlamb]

I renamed GetModuleBaseAddress -> GetUnwindInfoBaseAddress. It's documented as "returning the base address that the unwind info for a given CodeBlockHandle is relative to."

I changed all of cDAC to reference the base address using unwindInfoBase but left the pre-existing native references to moduleBase and imageBase.