Sync requirement and requirement issues state

What does this MR do and why?

This is part of state IIB of migrating requirements to work items(issues of type requirement).

Syncs state between issues(of type requirement) and requirements from both ends. Also makes sure no desync happens and if it happens logs an error.

• On UpdateRequirementService it uses a pseudo transaction to avoid desync already implemented on !64929 (merged)
• Issues::UpdateService and Issues::CloseService it uses a regular ActiveRecord transaction to avoid desync

related to #337190 (closed)

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

app/services/issues/close_service.rb

@@ -3,8 +3,8 @@
 module Issues
   class CloseService < Issues::BaseService
     # Closes the supplied issue if the current user is able to do so.
-    def execute(issue, commit: nil, notifications: true, system_note: true, skip_auth: false)
-      return issue unless can_close?(issue, skip_auth: skip_auth)
+    def execute(issue, commit: nil, notifications: true, system_note: true, skip_authorization: false)
+      return issue unless can_close?(issue, skip_authorization: skip_authorization)
 
       close_issue(issue,
                   closed_via: commit,
@@ -51,7 +51,7 @@ def close_issue(issue, closed_via: nil, notifications: true, system_note: true)
 
     private
 
-    # Overriden on EE
+    # Overridden on EE
     def perform_close(issue)
       issue.close(current_user)
     end
@@ -62,7 +62,7 @@ def issues_enabled?(issue)
     end
 
     # Overriden on EE
-    def can_close?(issue, skip_auth: false)
+    def can_close?(issue, skip_authorization: false)
       can?(current_user, :update_issue, issue) || issue.is_a?(ExternalIssue)
     end