chore(migration): Re-run database migration job for caching. (#8581)

A support request that came to Chatwoot Cloud revealed that the job was timed prematurely. The default timeout for Sidekiq queues was set as 25 minutes in sidekiq.yml file. The cache was not created properly for the accounts with more than 100k conversations.

This change removes the cache logic in the previous migration and creates a new migration with a new job which processes conversations in batch.

app/jobs/migration/conversation_batch_cache_label_job.rb

@@ -0,0 +1,14 @@
+class Migration::ConversationBatchCacheLabelJob < ApplicationJob
+  queue_as :async_database_migration
+
+  # To cache the label, we simply access it from the object and save it. Anytime the object is
+  # saved in the future, ActsAsTaggable will automatically recompute it. This process is done
+  # initially when the user has not performed any action.
+  # Reference: https://github.com/mbleigh/acts-as-taggable-on/wiki/Caching
+  def perform(conversation_batch)
+    conversation_batch.each do |conversation|
+      conversation.label_list
+      conversation.save!
+    end
+  end
+end

app/jobs/migration/conversation_cache_label_job.rb

@@ -1,16 +1,9 @@
 class Migration::ConversationCacheLabelJob < ApplicationJob
   queue_as :async_database_migration
 
-  # To cache the label, we simply access it from the object and save it. Anytime the object is
-  # saved in the future, ActsAsTaggable will automatically recompute it. This process is done
-  # initially when the user has not performed any action.
-  # Reference: https://github.com/mbleigh/acts-as-taggable-on/wiki/Caching
   def perform(account)
-    account.conversations.find_in_batches do |conversation_batch|
-      conversation_batch.each do |conversation|
-        conversation.label_list
-        conversation.save!
-      end
+    account.conversations.find_in_batches(batch_size: 100) do |conversation_batch|
+      Migration::ConversationBatchCacheLabelJob.perform_later(conversation_batch)
     end
   end
 end