knqyf263/gost: db/redhat.go; 4 LoC

Found a possible issue in [knqyf263/gost](https://www.github.com/knqyf263/gost) at [db/redhat.go](https://github.com/knqyf263/gost/blob/3060e463e183010ebd1a9946718c819e914d408e/db/redhat.go#L22-L25)

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.

> function call which takes a reference to a at line 23 may start a goroutine

[Click here to see the code in its original context.](https://github.com/knqyf263/gost/blob/3060e463e183010ebd1a9946718c819e914d408e/db/redhat.go#L22-L25)

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

```go
for _, a := range all {
r.conn.Model(&a).Related(&a.Cvss3).Related(&a.Details).Related(&a.PackageState)
allCves = append(allCves, a)
}

```

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: 3060e463e183010ebd1a9946718c819e914d408e

Review db/redhat.go lines 22-25 at commit 3060e463e183010ebd1a9946718c819e914d408e, focusing on the range-loop reference passed to the chained calls. Use the linked classification guidance to decide whether the analyzer finding is a Bug, Mitigated, or Desirable Behavior, then leave the corresponding reaction; completion is the selected classification.

Written by the indexing model from the issue text.