Determine ABI transformation strategy based on type signature

Currently, we must hardcode the ABI transformation strategy for procedures in the Miden stdlib and tx kernel, as we do not have type signature metadata available in those packages (or any MASM-sourced package for that matter). This is obviously brittle and unsustainable.

Once #465 is implemented (probably with the addition of #466 to define the types for the stdlib/tx kernel procedures as part of the source code), we can refactor the code that handles ABI transformation strategies to instead dispatch based entirely on the type signature/ABI of a procedure, without needing to be aware of where that procedure is defined.

This will be an essential step in making the relationship between the compiler and the various other toolchain components (particularly packages/libraries) less brittle. See also #316 for discussion on what the future of working with such packages/libraries looks like in the future once this is implemented.

First, understand the current ABI transformation strategy hardcoding in the Miden stdlib and tx kernel. Review issues #465 and #466 for context on type signature metadata. Then, locate the code that handles ABI transformations and refactor it to dispatch based on type signature/ABI, independent of procedure definition location. Ensure the changes align with the future package/library workflow discussed in #316.

由索引模型根據 Issue 內容生成。