vshn/k8up: executor/prune.go; 3 LoC

Found a possible issue in [vshn/k8up](https://www.github.com/vshn/k8up) at [executor/prune.go](https://github.com/vshn/k8up/blob/fa2c9f95601c21e9fef8b666e95e4d2a59cd7e18/executor/prune.go#L101-L103)

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.

> reference to prune is reassigned at line 102

[Click here to see the code in its original context.](https://github.com/vshn/k8up/blob/fa2c9f95601c21e9fef8b666e95e4d2a59cd7e18/executor/prune.go#L101-L103)

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

```go
for i, prune := range pruneList.Items {
jobs[i] = &prune
}

```

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: fa2c9f95601c21e9fef8b666e95e4d2a59cd7e18

Start at executor/prune.go lines 101-103 and inspect the surrounding prune-list handling and any related tests. Run the relevant tests or reproduce the analyzer finding, then determine whether the referenced range-loop behavior is a bug, mitigated, or desirable behavior and record the classification reaction.

Written by the indexing model from the issue text.