rebuild for python3.12 + libpq16

[akrherz]

Checklist

• [x] Used a personal fork of the feedstock to propose changes
• [x] Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• [x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [x] Ensured the license file is being packaged.

Applies python 3.12 + libpq16 migrations to 2.x.x branch.

Anybody have thoughts on if 2.x.x should be added to abi migration so that it continues to receive migrations? psycopg 2 and psycopg 3 are not compatible and can live side-by-side, so folks like me will be running both into the foreseeable future as I work through migrating various code bases....

[conda-forge-webservices[bot]]

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.

[akrherz]

@conda-forge-admin please rerender

[xylar]

Thanks @akrherz!

[xylar]

CI seems to be getting hit pretty hard these days. I'll put the automerge label on and we'll see how it goes...

[akrherz]

Thanks @xylar , sorry about embedding my question above in the PR, but you have thoughts about adding an abi migration branch to main for this? I'd be happy to PR it, of course.

[xylar]

@akrherz, I see, I did miss that. Feel free to make a PR to main to add 2.x.x to migrations.

Update: done in #88

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!