flier/curator.go: state.go; 9 LoC

Found a possible issue in [flier/curator.go](https://www.github.com/flier/curator.go) at [state.go](https://github.com/flier/curator.go/blob/366ffb7709bf81b1eb91735a78fa45916f6eaad6/state.go#L266-L274)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> range-loop variable watcher used in defer or goroutine at line 272

[Click here to see the code in its original context.](https://github.com/flier/curator.go/blob/366ffb7709bf81b1eb91735a78fa45916f6eaad6/state.go#L266-L274)

Click here to show the 9 line(s) of Go which triggered the analyzer.

```go
for _, watcher := range s.parentWatchers.watchers {
go func() {
tracer := newTimeTracer("connection-state-parent-process", s.tracer)

defer tracer.Commit()

watcher.process(event)
}()
}

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 366ffb7709bf81b1eb91735a78fa45916f6eaad6

Read state.go lines 266-274 and the analyzer report first, then inspect the surrounding state-handling code to understand how each watcher is intended to process the event. Done means the goroutines reliably process their intended watchers without the reported range-loop capture issue, with the surrounding behavior checked for regressions.

Written by the indexing model from the issue text.