Fix race condition in config handling (main)

[f-blass]

Description of the Change

The CLI encounters race conditions when handling config files if multiple commands are executed in parallel.

Currently, the CLI writes a new config for every command executed due to the code in command_parser.go. However, it also deletes all temporary config files when reading the config, leading to race conditions between multiple processes. This PR introduces two changes to mitigate this problem:

1. Ignore "File Not Found" errors when attempting to delete a file. This change addresses the issue where multiple processes list and delete temporary files simultaneously.
2. Only delete temp config files older than 5 minutes. This change resolves the problem where one process creates a temporary config that it later wants to rename, while a second process deletes this temp config in the meantime. Orphan files should be rare, as they are normally pruned by the signal handler, as seen in

   cli/util/configv3/write_config.go

   Lines 63 to 66 in 04df8ae

   	func catchSignal(sig chan os.Signal, tempConfigFileName string) {
   	<-sig
   	_ = os.Remove(tempConfigFileName)
   	os.Exit(2)

Why Is This PR Valuable?

Enables usage of the CF CLI in scripts which execute commands in parallel

Applicable Issues

fixes #2232

How Urgent Is The Change?

Medium

Other Relevant Parties

Anyone using the CLI in scripts with parallel execution. Multiple users have encountered this issue, as discussed in #2232.

Related PRs

v7
v8

[gururajsh]

LGTM

[ryenus]

The condition check on the next line is for skipping the newer files. That's why it feels a little bit confusing to read this comment together with the next line.
It would be better to say something like: "skip newer files created within 5 minutes".
Nevertheless thank you @gururajsh so much for fixing this!

[f-blass]

Hi @gururajsh
do you know when there will be a new release which includes this fix?

[gururajsh]

Hi @f-blass
We are planning on doing a release this week which includes this fix. Will keep you posted.

[gururajsh]

Hi @f-blass ,
New CLI version has been released with this fix