chore: remove GODEBUG winsymlink=0 from go.mod (#102)

* chore: remove GODEBUG winsymlink=0 from go.mod

The winsymlink=0 flag preserved pre-Go-1.23 behavior where Windows
directory junctions were treated as symlinks.  Go 1.23+ defaults to
treating junctions as regular directories (winsymlink=1), which is the
correct modern behavior.  Go 1.26 deprecates the flag entirely.

Affected code paths (copy_dir.go, filesystem_search.go,
communicator.go, command_test.go) already handle real symlinks
correctly and are unaffected by this change on Linux/macOS.  On
Windows, junctions will now be traversed as directories rather than
followed as symlinks, matching upstream opentofu#3415.

Closes #53

* chore: normalize godebug directive to single-line form after go mod tidy

Author: vmvarela

go.mod

@@ -5,10 +5,7 @@ go 1.26
 // At the time of adding this configuration, the new Go feature introduced here https://github.com/golang/go/issues/67061,
 // was having a good amount of issues linked to, affecting AWS Firewall, GCP various services and a lot more.
 // In go1.23 the godebug flag for this was named 'tlskyber', renamed in go1.24 to 'tlsmlkem'. https://tip.golang.org/doc/godebug#go-124
-godebug (
-	tlsmlkem=0
-	winsymlink=0 // See https://github.com/opentofu/opentofu/pull/3289
-)
+godebug tlsmlkem=0
 
 require (
 	cloud.google.com/go/kms v1.26.0