Dear dh-go maintainer,


While porting goxkcdpwgen from experimental to unstable. I noticed the
legacy DefaultGODEBUG flags are still appears in the built binary.

In debian/rules of goxkcdpwgen package, I have append these lines to
check the DefaultGODEBUG:
```
execute_after_dh_auto_install:
        @echo "=== Printing Go build metadata ==="
        # Dynamically finds and inspects any compiled binaries in the staging directory
        find debian/*/usr/bin/ -type f -executable -exec go version -m {} +
        @echo "=================================="
```

I got these in the build log:
=== Printing Go build metadata ===
# Dynamically finds and inspects any compiled binaries in the staging directory
find debian/*/usr/bin/ -type f -executable -exec go version -m {} +
debian/tmp/usr/bin/goxkcdpwgen: go1.27.0
	path	github.com/martinhoefling/goxkcdpwgen
	mod	github.com/martinhoefling/goxkcdpwgen	(devel)
	build	-buildmode=exe
	build	-compiler=gc
	build	-trimpath=true
	build	DefaultGODEBUG=containermaxprocs=0,cryptocustomrand=1,decoratemappings=0,gotestjsonbuildtext=1,httpcookiemaxnum=0,httplaxcontentlength=1,httpmuxgo121=1,httpservecontentkeepheaders=1,multipathtcp=0,netedns0=0,panicnil=1,randseednop=0,rsa1024min=0,tlsmlkem=0,tlssecpmlkem=0,tlssha1=1,tracebacklabels=0,updatemaxprocs=0,urlmaxqueryparams=0,urlstrictcolons=0,winreadlinkvolume=0,winsymlink=0,x509negativeserial=1,x509rsacrt=0,x509sha256skid=0,x509sslcertoverrideplatform=0,x509usepolicies=0
	build	CGO_ENABLED=1
	build	GOARCH=amd64
	build	GOOS=linux
	build	GOAMD64=v1
==================================

You may simply reproduce it by following steps:

1. Fetch goxkcdpwgen package from
https://salsa.debian.org/go-team/packages/goxkcdpwgen

2. Checkout debian/experimental branch.

3. Update build-deps to use dh-go

4. Run: sbuild --chroot-mode=unshare --no-clean-source -d unstable


Best regards,