Fix spurious versions from touch events with no changes

Previously, `changed_notably?` in `Events::Update` returned `true` for
touch events even when `changes_in_latest_version` was empty. This
caused spurious version records to be created, particularly when using
ActiveStorage, which calls `touch` after attaching blobs.

By removing this override, we now delegate to the base class
implementation, which only creates versions when there are actual
notable changes tracked by Rails' dirty tracking.

Fixes #1465

Author: mattmenefee

lib/paper_trail/events/update.rb

@@ -37,19 +37,16 @@ def data
         merge_metadata_into(data)
       end
 
-      # If it is a touch event, and changed are empty, it is assumed to be
-      # implicit `touch` mutation, and will a version is created.
+      # NOTE: We previously overrode `changed_notably?` here to return `true`
+      # for touch events even when `changes_in_latest_version` was empty.
+      # This caused spurious versions when used with ActiveStorage, which
+      # calls `touch` after attaching blobs without making meaningful changes.
       #
-      # See https://github.com/rails/rails/commit/dcb825902d79d0f6baba956f7c6ec5767611353e
+      # By removing the override, we now delegate to the base class, which
+      # only creates versions when there are actual notable changes.
       #
-      # @api private
-      def changed_notably?
-        if @is_touch && changes_in_latest_version.empty?
-          true
-        else
-          super
-        end
-      end
+      # See https://github.com/paper-trail-gem/paper_trail/issues/1465
+      # See https://github.com/rails/rails/commit/dcb825902d79d0f6baba956f7c6ec5767611353e
 
       private