Fix concurrent map access race in network-ports module and bump version to 2.0.5

[jbarciabf]

Summary

Fixes the concurrent map read/write panic in NetworkPortsModule reported in #129, hardens worker-goroutine counter access fleet-wide, updates GitHub Actions for Node 24 compatibility, and bumps version to 2.0.5.

Bug 1: Concurrent map read/write panic in network-ports (Fixes #129)

NetworkPortsModule cached EC2 NACLs and Security Groups in two per-region maps. The cache lookup read the maps without holding a lock while the cache population path took a write lock, producing a concurrent map read and map write runtime panic when multiple region goroutines hit the cache check concurrently. Reproduced reliably in low-density AWS accounts where every region goroutine raced through the cache check at the same instant.

Fix: take the read lock on the cache fast-path in both getEC2NACLsPerRegion and getEC2SecurityGroupsPerRegion. naclsMutex and securityGroupsMutex moved from package-level vars to struct fields so concurrent module instances stop serializing on each other's locks.

Bug 2: Torn integer writes in CommandCounter

CommandCounter used plain int fields with naked ++/-- from worker goroutines, while SpinUntil read them concurrently. Plain int increments are not atomic in Go: lost updates and torn reads were possible across both AWS and GCP modules, producing inconsistent progress display and drifted Error counts. Not a panic, but a silent correctness bug.

Fix: convert CommandCounter fields to int64 with Incr*/Decr*/Load* methods backed by atomic.AddInt64 and atomic.LoadInt64. Plain int64 storage keeps the struct copyable so existing constructors and helpers that take modules by value continue to vet-clean (no noCopy fanout). 1087 call sites updated across aws/, gcp/commands/, and internal/gcp/.

Bug 3: Stale GitHub Actions before Node 24 enforcement

actions/checkout v4, actions/setup-go v4, and marvinpinto/action-automatic-releases all run on Node 20, which becomes unsupported on June 2, 2026.

Fix: upgrade actions/checkout to v6, actions/setup-go to v5, go-version to ^1.25 (matches project), and replace the abandoned marvinpinto/action-automatic-releases with softprops/action-gh-release@v2.

Testing

• go build ./... clean
• go vet ./... warning count unchanged from main (zero new warnings)
• go test -race -run TestNetworkPorts ./aws/ passes
• Regression test added (TestNetworkPortsCacheConcurrentAccess): with the read lock removed, go test -race reports the mapaccess2_faststr read racing the locked write; with the fix in place the test passes