Use after_commit instead of after_destroy_commit

The bugfix on Mongoid is not released yet, but that should not matter
since there is no real reason to turn this back to after_destroy_commit.

The behavior is equivalent.

Author: ellnix

lib/meilisearch-rails.rb

@@ -482,9 +482,8 @@ def meilisearch(options = {}, &block)
                 super(*args)
               end
             end
-          # Currently after_destroy_commit is broken in Mongoid
-          elsif respond_to?(:after_destroy) && !Utilities.mongo_model?(self)
-            after_destroy_commit { |searchable| searchable.ms_enqueue_remove_from_index!(ms_synchronous?) }
+          elsif respond_to?(:after_destroy)
+            after_commit(on: :destroy) { |searchable| searchable.ms_enqueue_remove_from_index!(ms_synchronous?) }
           end
         end
       end