Nicer handling of erroring when filename+log do not match

[snipe]

This is a bit of a fringe case, but sometimes it happens that in the User > User Files section, there is a file that exists but no matching file on the server, or vice versa. This is usually due to a restore or manually edited data, but we weren't accounting for it before and would 500. Now we give a nice error message.

[what-the-diff]

PR Summary

• Additional Verification for User Existence
  Before deleting any user data, this update adds an extra layer of verification to confirm that the user exists in the first place. This contributes to the overall integrity of the data and service.

• Modified Delete Authorization Check
  The authorization process for deleting user files has been adjusted to align more precisely with our updated security standards.

• Updated File Destination Path
  The storage location for uploaded files has been shifted. This change helps us organize and manage files more effectively.

• Enhanced File and Action Log Deletion Process
  We have reworked the method of deleting files and their accompanying action logs, ensuring a more clean and thorough removal of data.

• Added Validation for File Existence before Deletion
  We are ensuring the existence of files before attempting any deletion. This can prevent unnecessary errors and improve efficiency.

• Improved Messages after File Deletion
  The user will now receive a more informative message following successful file deletion, enhancing user experience.

• Updated User not Found Error Message
  In cases where the user cannot be found, the error message has been updated to better communicate the issue.

• Improved Redirect after User Not Found
  If a user is not found, the redirection process has been revised to better manage the situation.