Fix the arguments and the lookup of super

[sinsoku]

Motivation / Background

This Pull Request has been created because TypeProf reports valid calls of super as errors.

class A
  def foo(x, y) = [x, y]
  def bar(x) = x
end
class B < A
  def foo(x = 0, y = "str")
    super             # wrong number of arguments (0 for 2)
  end
  def bar(x)
    [1].map { super } # undefined method: B#map
  end
end
B.new.foo
B.new.bar(1)

Detail

• A bare super passes the current values of the parameters, including defaults and reassignments, but TypeProf forwarded only what the caller gave, sharing the implementation of ... (Handle mixed and omitted forwarded arguments #434). ... and anonymous or destructured parameters are still forwarded that way, as they have no variable the method can reassign. A keyword default also did not reach the parent when the method had a named **rest that stayed empty, as the box merging the keywords into it never ran.
• A block took the name of the method it was passed to, so super in it looked up map. It now passes the variables of the method even where a block parameter shadows them. A super outside any method, such as in a define_method block in a class body, now skips the lookup, so it is no longer reported as an undefined method.

Verification

The example above reports no errors and infers A#foo: (Integer, String) and A#bar: (Integer). Each added scenario fails on the commit before its fix.

🤖 Generated with Claude Code