Call super from method_added/singleton_method_added methods

If a `method_added`/`singleton_method_added` method on a constant doesn't call `super` then none of the `method_added`/`singleton_method_added` methods on ancestors of the constant ever get called by Ruby.

This breaks any code that might want to instrument classes to collect method definition locations, or to do other things when methods are added.

In order to be a good citizen, it is best practice to call `super` from these methods.

Author: paracycle

activerecord/lib/active_record/scoping/named.rb

@@ -190,6 +190,7 @@ def scope(name, body, &block)
 
         private
           def singleton_method_added(name)
+            super
             # Most Kernel extends are both singleton and instance methods so
             # respond_to is a fast check, but we don't want to define methods
             # only on the module (ex. Module#name)

activesupport/lib/active_support/current_attributes.rb

@@ -182,6 +182,7 @@ def respond_to_missing?(name, _)
         end
 
         def method_added(name)
+          super
           return if name == :initialize
           return unless public_method_defined?(name)
           return if respond_to?(name, true)

activesupport/lib/active_support/subscriber.rb

@@ -67,6 +67,7 @@ def detach_from(namespace, notifier = ActiveSupport::Notifications)
 
       # Adds event subscribers for all new methods added to the class.
       def method_added(event)
+        super
         # Only public methods are added as subscribers, and only if a notifier
         # has been set up. This means that subscribers will only be set up for
         # classes that call #attach_to.