Increase file lock timeout to fix flaky CI test (#4004)

The concurrent secrets test was failing on GitHub Actions with
"context deadline exceeded" when 10 goroutines raced to acquire
the same file lock. Each lock holder performs AES encryption and
a disk write, which on slow CI runners could easily exceed the
previous 1-second timeout when requests queue up.

Increasing the timeout to 5 seconds provides enough headroom for
concurrent operations on slow hardware without meaningfully
impacting real-world responsiveness.

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: reyortiz3

pkg/fileutils/lock.go

@@ -13,7 +13,7 @@ import (
 
 const (
 	// DefaultLockTimeout is the maximum time to wait for a file lock.
-	DefaultLockTimeout = 1 * time.Second
+	DefaultLockTimeout = 5 * time.Second
 
 	// defaultLockRetryInterval is the interval between lock acquisition attempts.
 	defaultLockRetryInterval = 100 * time.Millisecond