FR: Add Interfaces to Destroy File Database Entries

[Gykes]

This PR allows users to delete database duplicate entries via the playground. I was able to add a dummy secondary data to some images that were located in my database and then delete them accordingly.

For WP: I changed up the verbage of the variables a little bit as I felt like "DestroyFiles" could be misinterpreted by users. I kept the logic the same but modified it to "DestroyFileEntries"

This example deletes an entry with the ID of 10:

mutation {                                                                                                         
    deleteFileEntries(ids: ["10"])                                                                         
  }  

This is an example of removing a primary entry. It should error out and let the user know that it is a primary entry:

{
  "errors": [
    {
      "message": "cannot destroy primary file entry /Users/gykes/Desktop/blah.mkv",
      "path": [
        "deleteFileEntries"
      ]
    }
  ],
  "data": null
}

Also added destroy_file_entry option to SceneDestroyInput, ScenesDestroyInput, ImageDestroyInput, ImagesDestroyInput, and GalleryDestroyInput. This allows deleting the file DB entry (without removing the actual file) when destroying content.

fixes: #6355

[WithoutPants]

For WP: I changed up the verbage of the variables a little bit as I felt like "DestroyFiles" could be misinterpreted by users. I kept the logic the same but modified it to "DestroyFileEntries"

You've named it deleteFileEntries which is inconsistent with other destroy operations. I personally think destroyFiles is fine, assuming that it is properly documented, but destroyFileEntries is still better than the current naming.