Report errors raised by Projects::DestroyService

Previously most errors raised by Projects::DestroyService were not
reported, only logged. That meant we were effectively discarding the
backtrace, which we have found that we need for pinpointing the source
of certain errors. This adds error reporting to the service to equip us
for faster, more efficient troubleshooting.

app/services/projects/destroy_service.rb

@@ -41,6 +41,8 @@ module Projects
 
       true
     rescue StandardError => error
+      context = Gitlab::ApplicationContext.current.merge(project_id: project.id)
+      Gitlab::ErrorTracking.track_exception(error, **context)
       attempt_rollback(project, error.message)
       false
     rescue Exception => error # rubocop:disable Lint/RescueException

spec/services/projects/destroy_service_spec.rb

@@ -78,6 +78,11 @@ RSpec.describe Projects::DestroyService, :aggregate_failures do
       end.not_to raise_error
     end
 
+    it 'reports the error' do
+      expect(Gitlab::ErrorTracking).to receive(:track_exception).and_call_original
+      destroy_project(project, user, {})
+    end
+
     it 'unmarks the project as "pending deletion"' do
       destroy_project(project, user, {})