pybind11: update to 2.13.5

[barracuda156]

This port must be at par with py-pybind11.
See: contourpy/contourpy#436 Closes: https://trac.macports.org/ticket/70648

Description

P. S. Why do we even have two pybind11 ports which are essentially independent?

Type(s)

• bugfix
• enhancement
• security fix

Tested on

macOS 10.6
Xcode 3.2

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• referenced existing tickets on Trac with full URL in commit message?
• checked your Portfile with port lint --nitpick?
• tried existing tests with sudo port test?
• tried a full install with sudo port -vst install?
• tested basic functionality of all binary files?
• checked that the Portfile's most important variants haven't been broken?

[macportsbot]

Notifying maintainers:
@MarcusCalhoun-Lopez for port pybind11.

[Schamschula]

I also recently noticed the parallel existence of pybind11 and py-pybind11.

For what it's worth, I've been using pybind11 @2.13.5 in my local tree since August 23rd.

[barracuda156]

@Schamschula At the very minimum both versions should match, so that we do not get sudden breakages.

[reneeotten]

see my response in the Trac ticket you opened (https://trac.macports.org/ticket/70648 and thus should be closed by this PR, if merged). We should resolve this situation IMHO in one of the ways I mention there - not just by keeping this separate but identical port as you do here.