Add missing run_exports in cuda-cupti-dev

[traversaro]

Fix #9

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-webservices]

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) and found it was in an excellent condition.

[traversaro]

@conda-forge-admin, please rerender

[vyasr]

Yup this looks like an oversight on our part. Thanks!

[bdice]

Thanks for this fix!

As a note: I double-checked the SONAME / version compatibility of cupti. Prior to CUDA 12, linking to libcupti would break CUDA Enhanced Compatibility (runtime compatibility within the same major version) because it required the same major.minor version of CUDA. It seems that restriction has been lifted in CUDA 12.0 and later. That would've meant we needed different compatibility rules here but I think we are all good.

[vyasr]

We're doing a bit more investigation here as to whether there are issues with CEC in the rest of the dependency tree here.

[vyasr]

There are some subtleties around usage of cupti because some of its features involve other packages like nvperf that do not fully support CEC yet, and would therefore necessitate different pinnings in the run export. However, standalone usage of cupti is safe, so we're good with merging this PR for now and improving documentation of those edge cases over time.

[traversaro]

There are some subtleties around usage of cupti because some of its features involve other packages like nvperf that do not fully support CEC yet, and would therefore necessitate different pinnings in the run export. However, standalone usage of cupti is safe, so we're good with merging this PR for now and improving documentation of those edge cases over time.

Thanks a lot!