Fix incorrect PyBind11 headers target reference

[zachcran]

Is this pull request associated with an issue(s)?
No.

Description
The current name used to reference the PyBind11 headers target (pybind11_headers) only exists if PyBind11 is built with your project. If it is already installed, the exported target is instead pybind11::headers. During the build, pybind11_headers is aliased to pybind11::headers (here), so using pybind11::headers exclusively should work in both scenarios.

TODOs

• ParallelZone may need to be updated first for this to pass.

[zachcran]

ParallelZone uses nwx_add_pybind11_module() from the NWXCMake repository, while this repo does not. nwx_add_pybind11_module() is still finding the incorrect pybind11_headers, so I think these CI passing tests are potentially a false positive.

I would advise against merging this until:

• nwx_add_pybind11_module() is fixed (Fix incorrect PyBind11 headers target reference NWXCMake#51)
• ParallelZone has a passing build with the fix (Manually triggered test after Add separate workflow to manually trigger the CI tests on master ParallelZone#148)
• The CI here is rerun with both the NWXCMake and ParallelZone fixes in place

[ryanmrichard]

I'll probably forget about this PR while you work on the other issues. Please ping us again when this is r2g.

[zachcran]

@ryanmrichard @jwaldrop107 This should be r2g now. I made another commit updating a comment to make the tests rerun.

[jwaldrop107]

🚀 [bumpr] Bumped!
New version:v1.0.44
Changes:v1.0.43...v1.0.44