Indirect dependency lukechampine.com/uint128 fails TLS validation in migrate v4.19.1 #1367

Describe the Bug
go get github.com/golang-migrate/migrate/v4@v4.19.1 fails due to a broken TLS certificate on an indirect dependency. The module lukechampine.com/uint128 is listed as indirect in migrate v4.19.1, but the host's certificate is valid only for www.lukechampine.com, causing Go module fetches to fail.

Steps to Reproduce

1. Create a new Go module: go mod init test-migrate
2. Run: go get github.com/golang-migrate/migrate/v4@v4.19.1
3. Observe TLS error:

   get "https://lukechampine.com/uint128?go-get=1": x509: certificate is valid for www.lukechampine.com, not lukechampine.com
   

Expected Behavior
Go should be able to fetch migrate/v4 and its indirect dependencies without failing due to TLS errors.

Migrate Version
v4.19.1

Loaded Source Drivers
file
(go get does not load source drivers, this is just a module fetch issue)

Loaded Database Drivers
postgres
(go get does not load database drivers, this is just a module fetch issue)

Go Version
go version go1.25 darwin/amd64

Stacktrace

go: git.i.mercedes-benz.com/mbos/heron-go/v2: github.com/golang-migrate/migrate/v4@v4.19.1 requires
        lukechampine.com/uint128@v1.2.0: unrecognized import path "lukechampine.com/uint128": https fetch: Get "https://lukechampine.com/uint128?go-get=1": tls: failed to verify certificate: x509: certificate is valid for www.lukechampine.com, not lukechampine.com

Additional context

• This problem occurs even though lukechampine.com/uint128 is only an indirect dependency in migrate/v4.
• Using GOPROXY=https://proxy.golang.org,direct can bypass the issue temporarily, but the root cause is the broken TLS certificate on the upstream host.
• This breaks fresh builds or builds on machines without the module cached.