I don't want to be an ass, but why didn't you do such elementary research before filing a bug report?
I don't want to be an ass, too, but the fact that you searched for exactly "powersave frequency governor" and “Intel p-state” (and NOT something else) is elementary to YOU. I saw the Archlinux page but was (and still am) unsure of how much of what is said there applies to Debian. Heaven knows how differently you and them configure the kernels (and surely you and them don't take exactly the same kernels anyway).
As for https://www.kernel.org/doc/html/v6.1/admin-guide/pm/intel_pstate.html , it's dated 2017 (and no later year is mentioned!), whereas the processor in #1038981 is from Q2'20, and the kernel is from 2023 (6 years later than the document date). So even if I had found that document myself, I might have dismissed it just based on date. (To compare, certain configuration files, such as /etc/lvm.conf or /etc/default/grub, get partially outdated with every upgrade of Debian stable.) Anyway, does CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE still exist and, if so, is this configuration option off in Debian kernels? That's what seems to be the case based on https://www.google.com/search?q="CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE"+amd64+site%3Adebian.org , but I can't be sure …
The original, user-level and high-level bug was that I noticed that I couldn't provably limit the processor speed via tlp after an upgrade from Debian 11 to Debian 12. It took me quite a while (many hours spread over a few days) to get from that high level to the level of #1038981, and, as you surely understand, at a certain point I have to declare the boundary of my current expertise.
Gratefully, AlMa