`=no` values for sanitizer configure options still enable sanitizer flags

Bug report

Bug description:

Summary

Passing no to a sanitizer option is reported as disabled, but the option's action still adds sanitizer compiler and linker flags. For AddressSanitizer, it also disables pymalloc.

Reproduction

mkdir build
cd build

../configure --with-address-sanitizer=no
grep -E '^(BASECFLAGS|LDFLAGS)=' Makefile
grep WITH_PYMALLOC pyconfig.h

Actual Behavior

Configure reports:

checking for --with-address-sanitizer... no
checking for --with-pymalloc... no

Despite that output, the AddressSanitizer action adds -fsanitize=address to BASECFLAGS and LDFLAGS, and sets with_pymalloc=no.

Expected Behavior

--with-address-sanitizer=no should not enable AddressSanitizer flags and should not change the pymalloc setting. It should have the same result as omitting the option or using the corresponding --without-... form.

CPython versions tested on:

CPython main branch

Operating systems tested on:

Linux

Linked PRs

• gh-157355

首先在 CPython 的 main 分支上執行所提供的 configure 重現，並檢查 sanitizer configure 選項的處理方式；該處理會加入 BASECFLAGS、LDFLAGS 並變更 with_pymalloc。完成的標準是：--with-address-sanitizer=no 不改變 sanitizer 旗標和 pymalloc 設定，與省略該選項或使用對應的 --without 形式時一致。