JobArtifactsDestroy GraphQL mutation should be consistent with REST API

The following discussion from !96431 (merged) should be addressed:

• @alberts-gitlab started a discussion:

  @leetickett I have some concerns with this new GraphQL mutation, that it does not behave in a consistent manner as the REST API.

  In the REST API:

  1. We check for an ongoing project statistics refresh and reject the API if it is ongoing. The reason for this is that we want to prevent concurrent removal of artifacts and recalculating of statistics, which would result in incorrect statistics.
  2. We use DeleteService, which also warns of ongoing project statistics refresh.

  https://gitlab.com/gitlab-org/gitlab/blob/b2f81043fed51ea6355df65b7108678004816140/lib/api/ci/job_artifacts.rb#L144-146

  Could you please follow up to make the GraphQL endpoint consistent with the REST API? 🙇