Prepare release v332

[heroku-linguist]

Commits since the last release:

• Set WEB_CONCURRENCY_SET_BY if appropriate (Set WEB_CONCURRENCY_SET_BY if appropriate #2015)
• Bump rubocop-rspec from 3.8.0 to 3.9.0 in the ruby-dependencies group (Bump rubocop-rspec from 3.8.0 to 3.9.0 in the ruby-dependencies group #2018)
• Bump sigstore/cosign/cosign from v3.0.3 to v3.0.4 in /builds (Bump sigstore/cosign/cosign from v3.0.3 to v3.0.4 in /builds #2020)
• Bump poetry from 2.2.1 to 2.3.1 (Bump poetry from 2.2.1 to 2.3.1 #2019)
• Bump uv from 0.9.24 to 0.9.26 (Bump uv from 0.9.24 to 0.9.26 #2016)

For the full diff, see the compare view:
v331...main

[edmorley]

$ make publish 
Checking environment...
Checking buildpack versions in sync...
Extracting changelog entry for this release...
remote: Enumerating objects: 1, done.
remote: Counting objects: 100% (1/1), done.
remote: Total 1 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
Unpacking objects: 100% (1/1), 875 bytes | 875.00 KiB/s, done.
From https://github.com/heroku/heroku-buildpack-python
   4f9718c6..f9ce6a68  main       -> origin/main

- Updated Poetry from 2.2.1 to 2.3.1. ([#2019](https://github.com/heroku/heroku-buildpack-python/pull/2019))
- Updated uv from 0.9.24 to 0.9.26. ([#2016](https://github.com/heroku/heroku-buildpack-python/pull/2016))
- The web server concurrency calculation profile script now sets the env var `WEB_CONCURRENCY_SET_BY="heroku/python"` if `WEB_CONCURRENCY` was set automatically by the buildpack. ([#2015](https://github.com/heroku/heroku-buildpack-python/pull/2015))

Deploy as v332 [y/n]? y

Creating GitHub release...
https://github.com/heroku/heroku-buildpack-python/releases/tag/v332

Publishing to the Heroku Buildpack Registry...
Two-factor code: ********************************************
Publishing buildpack heroku/python... done
Publishing buildpack was successful

 Version Released At              Status    
 ─────── ──────────────────────── ───────── 
 332     2026-01-26T11:23:58.952Z published