Ruby: Block for steps into self parameters in trackModuleAccess

[hvitved]

Since #10705, we apply an open-world assumption when resolving calls to singleton method, just like with calls to instance methods, so we should no longer track module accesses into self parameters. This removes false positive call graph edges like

class SingletonA
    def self.singleton1
    end

    def self.call_singleton1
        singleton1
    end

    def self.call_call_singleton1
        call_singleton1
    end
end

class SingletonB < SingletonA
    def self.singleton1
    end

    def self.call_singleton1
        singleton1 # should not be able to target `SingletonA:::singleton1` and `SingletonC:::singleton1`
    end
end

class SingletonC < SingletonA
    def self.singleton1
    end

    def self.call_singleton1
        singleton1 # should not be able to target `SingletonA:::singleton1` and `SingletonB:::singleton1`
    end
end

SingletonA.call_call_singleton1
SingletonB.call_call_singleton1
SingletonC.call_call_singleton1

Moreover, we were also not properly handling calls to self.new inside singleton methods defined via singleton classes.