Fix rubocop warnings

Author: cbliard

app/services/journals/create_service.rb

@@ -361,7 +361,7 @@ def insert_data_sql(predecessor, notes, cause)
     # will already have been increased so nothing needs to be done.
     # But if any of the associated data is updated or if only a cause or note is added, the journable would
     # otherwise not have receive an updated timestamp.
-    def touch_journable_sql(predecessor, notes, cause)
+    def touch_journable_sql(predecessor, notes, cause) # rubocop:disable Metrics/AbcSize
       if journable.class.aaj_options[:timestamp].to_sym == :updated_at
         sql = <<~SQL
           UPDATE

spec/models/work_package/work_package_acts_as_journalized_spec.rb

@@ -56,7 +56,8 @@
 
     # The below test was failing with the following error:
     # ERROR:  new row for relation "journals" violates check constraint "journals_validity_period_not_empty" (PG::CheckViolation)
-    # DETAIL:  Failing row contains (1178, WorkPackage, 481, 1252, , 2025-12-04 07:58:21.028586+00, 1, 2025-12-04 07:58:21.028586+00, Journal::WorkPackageJournal, 833, {}, empty, f).
+    # DETAIL:  Failing row contains (1178, WorkPackage, 481, 1252, , 2025-12-04 07:58:21.028586+00, 1,
+    #          2025-12-04 07:58:21.028586+00, Journal::WorkPackageJournal, 833, {}, empty, f).
     it "can add multiple comments right after creation" do
       work_package
       User.execute_as current_user do