Update to 1.24.3 and enable "megabuild"

[cbourjau]

A less ambitious version #171

Inspired by the pytorch feedstock the idea is to build the expensive part once and then to reuse the build-artifacts to cheaply build the Python bindings using the upstream static-linking. I tried dynamic linking in #171, but failed. The bindings call many internal functions not defined in the C-API. I managed to expose those in a hacky way on Unix, but failed on Windows.

One extra challenge in this feedstock compared to pytorch is that the vendored onnx-dependency recreates binding files for protobuf which invalidates large parts of the build cache. That invalidation kicks in for every second output.

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/23050247857. Examine the logs at this URL for more detail.}