Enable tegra (Jetson Orin) packages, remove CUDA 11 logic and change build string to preprend the build type

[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). 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/19785842618. Examine the logs at this URL for more detail.}

[traversaro]

@conda-forge-admin, please rerender

[conda-forge-admin]

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

I tried to rerender for you, but it looks like there was nothing to do.

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

[traversaro]

@conda-forge-admin, please rerender

[conda-forge-admin]

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

I tried to rerender for you, but it looks like there was nothing to do.

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

[traversaro]

@conda-forge-admin, please rerender

[traversaro]

@conda-forge-admin, please rerender

[traversaro]

@carterbox it is ok if I already migrate this package to tegra builds, or you prefer to wait for conda-forge/conda-forge-pinning-feedstock#7956 ? Thanks in advance!

[traversaro]

@carterbox it is ok if I already migrate this package to tegra builds, or you prefer to wait for conda-forge/conda-forge-pinning-feedstock#7956 ? Thanks in advance!

Thinking more about this, I guess it should be fine, there are not a lot of other feedstocks that depend on this one.

[carterbox]

Yes. You can start publishing packages for Tegra; it's just annoying to build them because we don't have a simple migration method yet.