Combine separate ConfigureNVBench calls to fix cpp conda builds

[gforsyth]

Description

Two PRs merged in quick succession each added a separate transform benchmark with the same name, leading CMake to get angry:

5b0a85b
8ca4bc4

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[bdice]

Thanks for this fix! We try to keep the CMake file lists alphabetized.

[gforsyth]

Thanks for this fix! We try to keep the CMake file lists alphabetized.

Question about general project guidelines -- is that alphabetization something blocking this? Do we want to re-run CI for that cosmetic change or try to fix it in a follow-up alongside other packaging changes?

[lamarrr]

Thanks for the fix!

[davidwendt]

Thanks for this fix! We try to keep the CMake file lists alphabetized.

Question about general project guidelines -- is that alphabetization something blocking this? Do we want to re-run CI for that cosmetic change or try to fix it in a follow-up alongside other packaging changes?

CI is barely half way through so if you could push a fix now then the current run will automatically be cancelled.
Otherwise, it is probably not worth holding up a merge.

[bdice]

I agree with David here. I left that as an optional fix / for future awareness. I did consider applying the commit myself, to avoid a time-delay that might leave us in a hard decision (this passed, should we merge or apply the fix?). I probably should've applied it immediately.

I think you made the right call, and we can add a /merge so this goes in quickly to unblock other builds.

[bdice]

/merge