refactor: ignore already closed error

[KnisterPeter]

This hides the file already cloesd error as it is
distracting in the output and does not provide any value.

[github-actions]

MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ CREDENTIALS	secretlint	yes		no	1.01s
✅ EDITORCONFIG	editorconfig-checker	1		0	0.02s
✅ GIT	git_diff	yes		no	0.01s

See errors details in artifact MegaLinter reports on CI Job page
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

[codecov]

Codecov Report

Merging #1285 (d8c4f5d) into master (4f8da0a) will increase coverage by 4.11%.
The diff coverage is 74.22%.

@@            Coverage Diff             @@
##           master    #1285      +/-   ##
==========================================
+ Coverage   57.50%   61.62%   +4.11%     
==========================================
  Files          32       40       +8     
  Lines        4594     5529     +935     
==========================================
+ Hits         2642     3407     +765     
- Misses       1729     1850     +121     
- Partials      223      272      +49     

Impacted Files	Coverage Δ
pkg/model/action.go	0.00% <0.00%> (ø)
pkg/model/step_result.go	0.00% <ø> (ø)
pkg/container/docker_run.go	14.03% <14.88%> (+8.49%)	⬆️
pkg/container/docker_pull.go	33.33% <33.33%> (ø)
pkg/container/file_collector.go	43.11% <43.11%> (ø)
pkg/common/git/git.go	50.00% <47.91%> (ø)
pkg/container/docker_auth.go	47.61% <50.00%> (+2.61%)	⬆️
pkg/model/workflow.go	54.32% <50.00%> (+3.40%)	⬆️
pkg/exprparser/interpreter.go	73.37% <53.48%> (-0.02%)	⬇️
pkg/model/planner.go	50.73% <60.00%> (+0.32%)	⬆️
... and 30 more

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

[mergify]

@KnisterPeter this pull request has failed checks 🛠

[ChristopherHX]

You also removed the nil check for the error, this could cause a log print with a nil err.

No I didn't test this change yet

[KnisterPeter]

I've tested it and it's fine

[ChristopherHX]

I couldn't trigger a nil error print, other than that it looks much cleaner than in the initial PR

We need to pin the linter version, it doesn't make sense to get a red check for existing code due to new linting rules