…0276)

While trying to implement struct support for Swift reverse pinvokes I ended up
having to factor the ABI classification out of `lvaInitUserArgs` to be able to
invoke it multiple times for structs. In the end that led me to do the work to
split out the ABI classification into a different classifier for each ABI.

ARM32, LA64 and RV64 still need to be split out.

We still don't actually use this information for anything, but it's asserted
that it is correct. We are going to be using it in the backend for Swift reverse
pinvokes, and I expect to move more and more things to use it and get completely
rid of the ABI classification within `lvaInitUserArgs` (and in the long run
hopefully `CallArgs::AddFinalArgsAndDetermineABIInfo`).

Another todo: this classification should be where we determine whether something
is passed implicit by reference instead of doing that in
`lvaSetStruct`/`getArgTypeForStruct`.

…100450)

Add one job that runs JitOptRepeat on all functions, 2 repetitions.

…JS function (#100408)

* Fix more diagnostics with CA2263

* Apply feedbacks

Python 3.12 prints some warnings when parsing superpmi.py due to some
insufficiently escaped characters in some strings.

…ng intermediate artifacts. (#100528)

…OSX (#99986)

* Enable FEATURE_PERFMAP on OSX, and update perfjitdump.cpp to work on OSX

* Update PerfMapEnabled documentation

* Enable only on OSX, and use PlatformGetCurrentThreadId

* Manual mach_absolute_time calls

* Use QueryPerformanceCounter

* Cleaner QueryPerformanceFrequency verification

* Use FEATURE_PERFMAP

* Put back conditional, but all __APPLE__

* Fix logic error when disabling jitdump

Slight cleanup of `fx_resolver_t` and `NativeHostApis` tests in preparation for #99027:
- Collapse `reconcile_fx_references_helper` into `reconcile_fx_references`
- Make `NativeHostApis` tests / `HostApiInvokerApp` more consistent in how they log and validate results