[v7] Remove workaround for ppc64le emulation failure and bump build number to 11

[traversaro]

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.

[traversaro]

@conda-forge-admin, please rerender

[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). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.

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

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub Actions workflow below for more details. You can also ping conda-forge/core (using the @ notation) for further assistance or you can try rerendering locally.

The following suggestions might help debug any issues:

• Is the recipe/{meta.yaml,recipe.yaml} file valid?
• If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnnings.
• Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

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

[traversaro]

@conda-forge-admin, please rerender

[h-vetinari]

@isuruf, I restarted the job here (now that conda-forge/admin-requests#1236 was merged), and it still seems to have an empty QEMU_LD_PREFIX. I guess this means something is going wrong in the ci-setup, e.g. here, or even just with the creation of the sysroot environment.

I saw something that's perhaps related in conda-forge/ctng-compilers-feedstock#162, where the creation of that environment failed

+++ mamba create -n sysroot_linux-aarch64 --yes --quiet sysroot_linux-aarch64=2.34
[...]
error    libmamba Could not solve for environment specs
    The following package could not be installed
    └─ sysroot_linux-aarch64 =2.34 * is not installable because it conflicts with any installable versions previously reported.
critical libmamba Could not solve for environment specs

despite the fact that the sysroot has no constraints that could conflict with anything. Perhaps this is a bug in mamba?