Use '-f' to allow for race condition (issue #38447)

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.

What does this MR do?

Addresses issue #38447 (closed) where jobs which share a GIT_CLONE_PATH race to delete each other's gitlab_runner_env

Why was this MR needed?

The current behavior since v17.7.0 is to fail a job which cannot delete gitlab_runner_env, even if the file doesn't exist because it was already deleted by another parallel job.

What's the best way to test this MR?

In a secondary stage, set GIT_STRATEGY to none and GIT_CLONE_PATH to a fixed value and parallelize many jobs in the same stage hitting the same clone path. They should all be able to attempt to delete gitlab_runner_env without failing jobs.

What are the relevant issue numbers?

Closes #38447 (closed)