Link project_bot user deletion audit event to its resource if possible

What does this MR do and why?

Related to #488166 (closed)

Currently, when deleting user with any user type, GitLab creates user_destroyed audit event. That audit event is linked to User. Meaning that only instance admins can see that audit event.

The goal of this MR to allow resource(group/project) owners see user_destroyed audit events that are related to the resource project_bot user deletion by linking that audit event to the resource if possible.

That MR also

• improves user_destroyed audit event creation by mentioning reason of the user deletion in the message
• ensures user_destroyed audit event is created even without current_user
  • I think we and users could benefit from having audit events about user deletions without current_user(when user is deleted from rails console for instance). See !167021 (comment 2137711286)

Screenshots or screen recordings

Before	After

How to set up and validate locally

1. Create project access token or group access token. (Under the hood it creates a user with project_bot type)
2. Revoke the token or simulate token expiration.
3. Visit the group/project's /audit_events page. You should see the event about the project_bot deletion with the reason in the message.

app/services/users/destroy_service.rb

@@ -58,6 +58,9 @@ def execute(user, options = {})
       # Load the records. Groups are unavailable after membership is destroyed.
       solo_owned_groups = user.solo_owned_groups.load
 
+      # Load the project_bot user resource. It is unavailable after membership is destroyed.
+      options[:project_bot_resource] ||= user.resource_bot_resource
+
       user.members.each_batch { |batch| batch.destroy_all } # rubocop:disable Cop/DestroyAll
 
       solo_owned_groups.each do |group|