pgsql: Use value of scram_iterations in mock_scram_secret().

Use value of scram_iterations in mock_scram_secret().

Presently, mock_scram_secret() always uses
SCRAM_SHA_256_DEFAULT_ITERATIONS, which poses an observable
response discrepancy hazard when scram_iterations is set to
something else. To fix, use the value of the configuration
parameter instead, and document that unauthenticated users can
discover the existence of roles with passwords created with
different iteration counts.

Reported-by: Radim Marek <radim(at)boringsql(dot)com>
Author: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Reviewed-by: Michael Paquier <michael(at)paquier(dot)xyz>
Reviewed-by: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Reviewed-by: Jacob Champion <champion(dot)p(at)gmail(dot)com>
Security: CVE-2026-14672
Backpatch-through: 16

Branch
------
REL_17_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/dec60e8ada4cd46d0201efea844a4b22cb06444e
Author: Nathan Bossart <nathan(at)postgresql(dot)org>

Modified Files
--------------
doc/src/sgml/config.sgml | 13 +++++++++++++
src/backend/libpq/auth-scram.c | 2 +-
2 files changed, 14 insertions(+), 1 deletion(-)