fix(state): guard StateEventChans iteration with StateEventChansLock

[Aamod007]

Purpose of PR?:

Fixes #2774

PushContainerEvent, PushNodeEvent and PushNamespaceEvent in KubeArmor/state/data.go iterate sa.StateEventChans without holding StateEventChansLock, while addStateEventChan/removeStateEventChan mutate the map and close the channels under that lock on every WatchState client connect/disconnect. Since the runtime handlers push events from separate goroutines (go dm.StateAgent.PushContainerEvent(...)), a client disconnecting mid-broadcast crashes the daemon with fatal error: concurrent map iteration and map write or panic: send on closed channel.

This PR takes StateEventChansLock.RLock() around the broadcast loop in all three functions. The sends are already non-blocking (select/default), so holding the read lock during fan-out is cheap, and because removeStateEventChan closes channels under the write lock, the read lock also rules out the send-on-closed-channel panic.

Does this PR introduce a breaking change?

No.

If the changes in this PR are manually verified, list down the scenarios covered::

• Added TestPushContainerEventRace which simulates WatchState clients connecting/disconnecting concurrently with container event pushes. On current main it fails under go test -race (data race between PushContainerEvent and removeStateEventChan) and also panics with send on closed channel. With this fix, go test -race -count=1 -run TestPushContainerEventRace ./state/ passes.
• go vet ./state/ clean.

Additional information for reviewer? :

Failure output on main without the fix:

WARNING: DATA RACE
Read at ... by goroutine 11:
  ...state.(*StateAgent).PushContainerEvent()  KubeArmor/state/data.go:85
Previous write at ... by goroutine 10:
  runtime.closechan()
  ...state.(*StateAgent).removeStateEventChan() KubeArmor/state/stateAgent.go:92
...
panic: send on closed channel

Checklist:

• Bug fix. Fixes state agent: Push*Event iterate StateEventChans without StateEventChansLock — daemon crash (concurrent map write / send on closed channel) #2774
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• PR Title follows the convention of <type>(<scope>): <subject>
• Commit has unit tests
• Commit has integration tests

[vee1e]

here i is already used in the for loop, so the compiler doesn't consider it unused, making the assignment pointless. It neither suppresses a compiler error nor does anything at runtime. i know its pedantic but still worth pointing out dead code.